Transport & discovery
Reliable HTTP and agent-readable discovery
Use POST for JSON-RPC, handle unsupported methods correctly and discover the deployed tools before calling them.
NEETBros engineering · Published
Milestone:
Use the stateless transport
The customer MCP answers JSON-RPC over POST with JSON responses and no persistent MCP session ID. JSON-only Accept headers are supported.
GET and DELETE return 405 Method Not Allowed with Allow: POST because this endpoint does not offer a separate event stream or persistent session to delete. A 405 should not restart account sign-in. Authentication failures on protected POST requests are handled separately.
Discover first, then call
The public server card describes tools, input schemas, authentication requirements and connection metadata. Check it or tools/list instead of assuming an old tool signature still applies.
Handle temporary network failures and rate limits with bounded backoff. Preserve the request identifier when recovering an interrupted operation so retries do not become duplicate work. The current tool reference explains the active interface.
What an agent should do
- Send JSON-RPC to the advertised customer endpoint using POST.
- Treat 405 as an unsupported method, not an authentication failure.
- Read required tool inputs and retry only recoverable failures with bounded backoff.