curl --request POST \
--url https://mcp.echozero.app/mcp \
--header 'Accept: <accept>' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'x-signature: <x-signature>' \
--header 'x-timestamp: <x-timestamp>' \
--data '
{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-03-26",
"capabilities": {},
"clientInfo": {
"name": "swagger",
"version": "1.0.0"
}
}
}
'MCP Protocol
MCP JSON-RPC over Streamable HTTP
Requires Authorize (x-api-key) and a JSON-RPC body. Use Accept: application/json, text/event-stream and Content-Type: application/json. First call is usually initialize; response includes mcp-session-id — send it on later requests as header mcp-session-id.
POST
/
mcp
curl --request POST \
--url https://mcp.echozero.app/mcp \
--header 'Accept: <accept>' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'x-signature: <x-signature>' \
--header 'x-timestamp: <x-timestamp>' \
--data '
{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-03-26",
"capabilities": {},
"clientInfo": {
"name": "swagger",
"version": "1.0.0"
}
}
}
'Authorizations
bearer-jwtapi-key
Headers
Body
application/json
Single JSON-RPC request or batch array.
- object
- object[]
The body is of type object.
Response
JSON or SSE per MCP transport. Response headers may include mcp-session-id (after initialize) and X-Mcp-Instance-Id (which replica served the request; use with load balancer sticky sessions). See MCP_DEPLOYMENT_SCALING.md.