Record tool calls through your MCP server (Telltale for MCP servers)

View as Markdown

POST /api/v1/mcp/calls · operationId recordMcpCalls

For developers: your server sends this request with a server key; it is not a button in the dashboard. To see the same information without code, open Tools › All tools in the dashboard.

Shapes only: unknown fields are refused, never dropped, so no argument, result, error text or header can be stored. Each call is one approved-route call with channel mcp, once per eventId; a bad call is rejected alone. Sent by the MCP adapter (/adapters/v1/mcp.js; see Telltale for MCP servers). There is no field for arguments, results or error text.

Authentication

Send Authorization: Bearer YOUR_SERVER_KEY (siteServerKey: Site server key in Authorization: Bearer <key> (the scheme is case-insensitive and required; a bare key is 401). Shown once on creation or rotation. Publishable keys cannot authenticate). Keep the server key in server-only configuration; never send it to a browser.

Request body

Content-Type: application/json (required)

JSON
{
  "server": {
    "name": "docs-server",
    "version": "1.4.0"
  },
  "calls": [
    {
      "eventId": "call_00000001",
      "tool": "search_docs",
      "startedAt": 1794268800000,
      "endedAt": 1794268801200,
      "outcome": "ok",
      "client": {
        "name": "claude-ai",
        "version": "1.0"
      },
      "accountId": "acct_456"
    }
  ]
}

Responses

Success body fields

Failures are not verdicts. Error bodies follow the Error schema: code is one of bad_request, unauthorized, session_reinit_required, forbidden, not_found, conflict, identity_required, payload_too_large, rate_limited, internal_error, service_unavailable, request_failed, approval_invalid, approval_used, approval_expired, approval_mismatch, step_up_not_held, step_up_mismatch, step_up_settled, step_up_expired, step_up_superseded, agent_tokens_disabled, tool_not_approved, tool_not_read_only. Errors and retries explains each code and what to do.

Example

curl
curl -sS -X POST 'https://app.trytelltale.dev/api/v1/mcp/calls' \
  -H "Authorization: Bearer $TELLTALE_SERVER_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"server":{"name":"docs-server","version":"1.4.0"},"calls":[{"eventId":"call_00000001","tool":"search_docs","startedAt":1794268800000,"endedAt":1794268801200,"outcome":"ok","client":{"name":"claude-ai","version":"1.0"},"accountId":"acct_456"}]}'
fetch
const response = await fetch("https://app.trytelltale.dev/api/v1/mcp/calls", {
  method: "POST",
  headers: {
    Authorization: 'Bearer ' + process.env.TELLTALE_SERVER_KEY,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "server": {
      "name": "docs-server",
      "version": "1.4.0"
    },
    "calls": [
      {
        "eventId": "call_00000001",
        "tool": "search_docs",
        "startedAt": 1794268800000,
        "endedAt": 1794268801200,
        "outcome": "ok",
        "client": {
          "name": "claude-ai",
          "version": "1.0"
        },
        "accountId": "acct_456"
      }
    ]
  }),
  signal: AbortSignal.timeout(5000)
});
const result = await response.json();

Machine-readable contract: openapi.json. Request builder: the API explorer shows every operation as curl; it sends requests only on a local dashboard.