MCP JSON-RPC entry point

curl --request POST \
  --url https://api.talkzilla.app/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "method": "<string>",
  "id": "<string>",
  "params": {}
}
'

{
  "jsonrpc": "2.0",
  "id": "<string>",
  "result": {},
  "error": {
    "code": 123,
    "message": "<string>",
    "data": {}
  }
}

MCP

MCP JSON-RPC entry point

Single endpoint dispatching all MCP methods by method field: initialize, ping, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get, completion/complete.

Two auth schemes accepted on Authorization: Bearer <token>: the mck_ prefix routes to API-key path; everything else (HS256 JWT) routes to the OAuth client_credentials path. See /.well-known/oauth-authorization-server for OAuth metadata.

Rate-limited per token: 60/min general, 10/hour for dangerous-op tools. Audit row written on every tools/call to audit_log with actor_kind='mcp'.

POST

curl --request POST \
  --url https://api.talkzilla.app/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "method": "<string>",
  "id": "<string>",
  "params": {}
}
'

{
  "jsonrpc": "2.0",
  "id": "<string>",
  "result": {},
  "error": {
    "code": 123,
    "message": "<string>",
    "data": {}
  }
}

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

jsonrpc

enum<string>

required

Available options:

2.0

method

string

required

params

object

Response

JSON-RPC response (success or error envelope).

jsonrpc

enum<string>

Available options:

2.0

result

object

error

object

Show child attributes

Telegram bot webhook delivery OAuth 2.0 authorization-server metadata (RFC 8414)