Send MCP JSON-RPC message
Send JSON-RPC request to the MCP server over HTTP streaming transport
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Headers
Account secure id for the target provider account (optional if x-account-id query parameter is provided)
Session id; omit for initialize, include for subsequent calls
Response format. Include text/event-stream to receive SSE, application/json for standard JSON, or both.
"application/json, text/event-stream"
Query Parameters
Parameter schema style: "nested" (default) groups by location, "flat_prefixed" flattens with location prefix, "flat_smart" flattens and only prefixes on name collision
nested, flat_prefixed, flat_smart Tool registration mode: "individual" (default) registers each action as a separate tool; "search_execute" registers two tools per linked account for a search-then-execute flow
individual, search_execute Body
JSON-RPC 2.0 message
JSON-RPC protocol version
"2.0"
JSON-RPC method name. Supported values: initialize, tools/list, tools/call.
"initialize"
Method parameters. Shape varies by method — see the request body examples.
Request id (string or number). Echoed back in the response.
Response
Processed successfully
"2.0"
Echoes the id from the request. null for protocol-level errors where the id could not be determined.
Present on success. Shape varies by method — see response examples.
Present on protocol-level failure. Tool-level failures use result with isError: true instead.