APIs that explain themselves
One URL. Zero SDKs. Just HTTP and HTML.
Give URL
→
Use API
What is NOMCP?
NOMCP is a convention for creating APIs that any LLM or human can understand instantly. Give an agent a single URL, and it can discover and use your entire API without SDKs, documentation portals, or complex auth flows.
Not a new protocol. A convention for using existing ones.
The Difference
MCP (Model Context Protocol)
- Run local MCP server process
- Configure JSON-RPC transport
- Install MCP SDK/client
- Parse tool schemas
- Handle capability negotiation
- Finally call a tool
NOMCP
- Give LLM the URL
- Use the API
✓
A Complete API
That's it. That's the whole API documentation AND entry point.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Notes API</title>
</head>
<body>
<h1>Notes API</h1>
<p>A simple note-taking service.</p>
<h2>Scope</h2>
<p>This token has <strong>read/write</strong> access.</p>
<h2>Endpoints</h2>
<h3><code>GET /notes</code></h3>
<p>List all notes.</p>
<h3><code>POST /notes</code></h3>
<p>Create a new note.</p>
<p>Body: <code>{"title": "...", "content": "..."}</code></p>
</body>
</html>How It Works
GET
https://api.example.com/tok_abc123/
→ Returns HTML describing available endpoints
POST
https://api.example.com/tok_abc123/notes
→ Creates a note, returns JSON
Key Principles
Zero Configuration
Just a URL. Nothing else needed.
Human Readable
It's just HTML you can read.
Web Native
HTTP + HTML. That's it.
Self-Contained
Everything in one document.
Scoped by Default
Permissions baked into the URL.