What is the MCP Protocol?
The Model Context Protocol (MCP) is an open standard for communication between AI clients (Claude, Cursor, Windsurf) and tool servers. GetMCP implements the MCP specification using the Streamable HTTP transport.Endpoint
Each GetMCP server exposes a single HTTP endpoint:| URL Part | Description |
|---|---|
{slug} | The server’s URL slug (e.g., my-weather-tools) |
{server_id} | Optional 16-hex-char security token |
Transport: Streamable HTTP
All MCP requests use the Streamable HTTP transport:| Method | Purpose |
|---|---|
POST | Send JSON-RPC requests (the primary method) |
GET | Open an SSE stream for server-initiated messages |
DELETE | Terminate a session |
OPTIONS | CORS preflight |
Headers
Required for POST requests:Mcp-Session-Id is not provided, a new session ID is generated and returned in the response.
Authentication (if server requires it):
JSON-RPC 2.0
All POST request bodies and responses follow the JSON-RPC 2.0 specification.Request Format
Response Format
Success:Batch Requests
GetMCP supports JSON-RPC batch requests — send an array of request objects and receive an array of responses:Notifications
Requests without anid field are notifications. GetMCP processes them but returns no response (HTTP 202).
Supported Methods
| Method | Description |
|---|---|
initialize | Negotiate protocol version and get server capabilities |
ping | Check server connectivity |
tools/list | List all available tools |
tools/call | Execute a specific tool |
Error Codes
| Code | Description |
|---|---|
-32700 | Parse error — invalid JSON |
-32600 | Invalid request — malformed JSON-RPC structure |
-32601 | Method not found |
-32602 | Invalid params |
-32603 | Internal error — server-side exception |