AnkraDocs
Console

API reference · Locations and tools

Model Context Protocol

1 operation of the Ankra Cloud API: The Model Context Protocol endpoints (docs/mcp.md). They carry JSON-RPC messages, not REST resources, and are never MCP tools themselves.

Send one MCP JSON-RPC message as the API token#

POST/mcp
Operation
send_mcp_message
Credentials
API token

The customer MCP server (Streamable HTTP, stateless; docs/mcp.md). The body is one JSON-RPC 2.0 message; requests are answered with one JSON-RPC response, notifications and client responses with 202 and no body. Only an API token is accepted, a read-only one included: every tool call is dispatched to the REST route it names, which decides with the token's scope and its user's role. Rate limited per token (429). GET /mcp answers 405: the server opens no event stream.

Request bodyapplication/json · JSONRPCMessage

Request body fields
FieldTypeDescription
jsonrpcrequiredstringOne of 2.0
idstring | integerAbsent on notifications.
methodstring
paramsobject

Responses

200The JSON-RPC response; protocol errors are JSON-RPC errors.application/json · JSONRPCResponse

200 response fields
FieldTypeDescription
jsonrpcrequiredstringOne of 2.0
idrequiredstring | integer | null
resultobject
errorobject
coderequiredinteger
messagerequiredstring
dataany
  • 400A malformed message, a batch, or (revision 2026-07-28) a header that disagrees with the body.
  • 401Not signed in, or the credential is invalid or expired.
  • 403A browser request from another origin.
  • 429The token's MCP rate limit is spent; see Retry-After.
  • defaultAny other error, usually 500.

Example

bash
curl -X POST "$ANKRA_CLOUD_API/mcp" \
  -H "Authorization: Bearer $ANKRA_CLOUD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "jsonrpc": "2.0"
}'