Developers

MCP

The only programmatic way to reach Canu.

Canu has no REST API. The agent is reachable in exactly two places: the Canu workspace, and the Model Context Protocol (MCP) server. The MCP server implements JSON-RPC 2.0 over Streamable HTTP with protocol version negotiation and bearer authentication, so you can use Canu from Claude, ChatGPT, Cursor, or any MCP-compatible client.

Endpoint

text
https://usecanu.com/api/public/mcp

Client configuration

json
{
  "mcpServers": {
    "canu": {
      "url": "https://usecanu.com/api/public/mcp",
      "headers": { "Authorization": "Bearer <CANU_MCP_TOKEN>" }
    }
  }
}

Tools exposed

  • get_financial_summary — cash, revenue, expenses, net burn and runway
  • get_spend_breakdown — where the money goes, by vendor and category
  • get_runway_goal — the active runway goal and constraints
  • calculate_scenario — project runway under a hypothetical change
  • list_opportunities — ranked savings opportunities
  • get_path_to_target — the sequence of changes that reaches the goal
  • list_transactions — recent normalized transactions
  • get_data_coverage — which connections are live and how fresh they are

All MCP tools are read-and-analyze only. Canu never executes a change through MCP. MCP access is available on Growth and above.