Skip to main content
POST
/
mcp
A valid request URL is required to generate request examples
{
  "id": "<string>",
  "result": {},
  "error": {
    "code": 123,
    "message": "<string>",
    "data": "<unknown>"
  }
}

Authorizations

​
Authorization
string
header
required

Scoped personal access token (cfp_…), validated by the stateless mcp and api_v2 firewalls. The effective permission is the intersection of the user's ACL, the token's scopes, and tenant isolation. The MCP gateway requires the matching mcp:* tool scope; the /api/v2/* surface (including the Config read API) additionally requires the api:full scope and an admin owner.

Headers

​
MCP-Protocol-Version
string

Requested protocol revision; the negotiated value is echoed on the response.

Body

application/json

A single JSON-RPC 2.0 request. Omit id to send a notification.

​
jsonrpc
enum<string>
required
Available options:
2.0
​
method
string
required

JSON-RPC method, e.g. tools/list, tools/call.

​
id

Request id; absent for a notification (which gets an empty 202).

​
params
object

Method parameters object.

Response

JSON-RPC response envelope. Carries result on success or error on an application-level failure (including framing/auth failures, which use a null id).

A single JSON-RPC 2.0 response. Exactly one of result / error is present.

​
jsonrpc
enum<string>
required
Available options:
2.0
​
id
required
​
result
object

Present on success.

​
error
object

Present on failure.