Endpoints
Authentication
Send credentials on every MCP request, including the firstinitialize:
x-api-key: <developer_api_key>, orAuthorization: Bearer <access_token>(API key or OAuth token)
x-signature, x-timestamp) are required for API-key auth. See API keys + HMAC. JWT/OAuth session tokens are exempt.
Session lifecycle
1
Initialize
POST /mcp with method: "initialize". Save the mcp-session-id response header.2
Send initialized notification
POST /mcp with method: "notifications/initialized" and the session header.3
Call tools / list resources
Include
mcp-session-id: <session> on all subsequent requests.4
Optional SSE stream
GET /mcp/sse with Accept: text/event-stream and the session header for server-push events.5
End session
DELETE /mcp with the session header when done.X-Mcp-Instance-Id for load-balancer sticky routing in multi-instance deployments.
Example initialize request
mcp-session-id from the response headers.
Example tools/list
Tools, resources, and scopes
Available MCP tools, resources, and prompts are scope-gated by the API key or OAuth token. Common scopes:
Tools forward to the same REST endpoints documented in the API Reference. Errors use JSON-RPC format - see Error codes.
See the full Tools Reference and Resources for the out-of-band catalog (no runtime
tools/list required).
OAuth for assistant directories
For ChatGPT, Claude, Gemini, and other directory submissions:
Fetch connector metadata:
Assistant setup (coming soon)
Coming soon:
npx skills add EchoZeroApp/skills and ez login are not yet public. Use API keys or OAuth today.