Browse documentation
Model Context Protocol endpoint
MCP over Streamable HTTP. Answers POST (requests and notifications), GET (the event stream) and DELETE (end a session) on this one path. Authenticate with the same key REST uses, on every request — a session never pins an authorization. The protocol version is negotiated; the server does not pin one. Send `accept: application/json, text/event-stream`. Tool errors arrive inside the JSON-RPC frame, so a suspended account or an exhausted quota comes back as a tool error rather than a status that would look to your client like the server had vanished.
post
/mcp Request
curl -X POST \
-H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/mcp"Responses
| Status | Meaning |
|---|---|
200 | A JSON-RPC response. |
202 | A notification was accepted. The body is empty — this is not a JSON-RPC message, and answering `{}` here breaks conforming clients. |
401 | Missing, unknown or revoked key. A key minted moments ago can answer 401 until it propagates to the serving fleet. |
The same call over MCP is a tool with these parameter names unchanged. See Errors for what to do with each status.