MCP connection reference
Protocol details for implementers.
DimerIQ uses Streamable HTTP POST and JSON-RPC 2.0. Authenticate each request with an app-specific bearer token. Send Content-Type: application/json and Accept: application/json, text/event-stream.
A typical client performs initialize, sends the initialized notification, calls tools/list, then uses tools/call. Prefer an established MCP SDK rather than treating this as arbitrary REST.
The service publishes protected-resource metadata and returns a WWW-Authenticate challenge when sign-in is required. API and MCP audiences are distinct. Validate returned tool schemas and respect their read/write annotations; the server independently enforces permissions.
A JSON-RPC HTTP 200 can still contain an error, or a tool result with isError: true. Check both before treating a call as successful. Responses may use JSON or event streams according to the negotiated transport.
See DimerIQ's tool list. The older search tools and new panel tools refer to different saved workflow objects; do not interchange their IDs.