MCP Connection

The MCP server exposes Clocktower protocol tools at mcp.clocktower.finance. Hosted MCP usage is governed by the Terms of Use.

Endpoint

https://mcp.clocktower.finance

The MCP client connects to the subdomain root — no /mcp path suffix.

Access

MCP uses the same free (per IP) and developer (ctk_…) lanes as REST. Each tool call counts against those rate limits. Mint a key at developers.clocktower.finance when you need higher read limits. See REST authentication.

Invalid or revoked keys fail the request (401). They do not fall back to the free tier.

Client setup

Connect using any MCP-compatible client. Your client must support:

1. MCP transport to mcp.clocktower.finance (Streamable HTTP; no /mcp path suffix)
2. Wallet signing for prepared transactions

Example client config (free tier — no key):

{
  "mcpServers": {
    "clocktower": {
      "url": "https://mcp.clocktower.finance"
    }
  }
}

With a developer key, send the same Authorization header REST uses:

{
  "mcpServers": {
    "clocktower": {
      "url": "https://mcp.clocktower.finance",
      "headers": {
        "Authorization": "Bearer ctk_…"
      }
    }
  }
}

Then call tools by name with JSON arguments. See the MCP quickstart.

Tool categories

Category	Examples
Read	list_chains, get_protocol_state, get_subscription, get_account
Discovery	search_subscriptions, get_subscription_details
History	get_subscription_history, get_account_activity
Write (prepare)	prepare_subscribe, prepare_create_subscription, prepare_remit
Status	get_transaction_status, check_subscribe_readiness

See Tools reference for the full list.

Protocol

• Chain: optional chainId on protocol tools; omitted uses Base (8453). See MCP chain selection.
• Auth: same free and developer credentials as REST
• Writes: prepare-only — server never relays signed transactions

REST uses ?chainId= on the query string. MCP uses a tool argument. SIWE and x402 payments stay on Base.