Connect Parakeeto to Claude or another MCP client

Parakeeto serves an MCP endpoint, so an AI assistant can read your accounts' reports and answer questions about them. The tools are read-only by default.

What you need

• The MCP URL: the Parakeeto backend origin followed by /mcp. This is the backend hostname, not the web app's.
• A Parakeeto sign-in.

Sign in with OAuth

The server supports OAuth with PKCE, dynamic client registration and client ID metadata documents. A client that supports remote MCP with OAuth connects without a key.

Claude (claude.ai and Claude Desktop). Add a custom connector and enter the MCP URL. Anthropic's article Getting started with custom connectors using remote MCP lists the steps.

Claude Code. Add the server, then authenticate from /mcp:

claude mcp add --transport http parakeeto <MCP URL>

Other MCP clients. Any client that supports Streamable HTTP and OAuth authorization can connect.

The client opens three Parakeeto pages in turn:

1. Sign in, on /mcp/login.
2. Choose accounts, on /mcp/accounts.
3. Approve the connection, on /mcp/consent.

Choose accounts

A connection reaches only the accounts you select at sign-in, and only while you still have access to them. Parakeeto recomputes that reach on every request, so removing your access to an account removes the assistant's too. The assistant calls list_accounts to see what it can reach. See permissions.

What an assistant can and cannot see

• Read-only tools are the default. The assistant can read reports and cannot change data.
• Each tool's page states its limits. For example, where a tool says no compensation or person-level data is returned, none is. See tools and permissions.
• Administrative tools appear only when an administrator opts in by connecting at /mcp?tools=admin.
• API keys never grant administrative tools, including keys an administrator owns.
• Review or revoke a connection on /mcp/connections.

API keys

Administrators can connect a client that has no OAuth support with an API key. An administrator issues the key, scoped to all accounts or an allow-list, from the API keys page. The assistant sends it as Authorization: Bearer <key> on every request.

The methodology resource

The resource parakeeto://methodology holds the review principles an assistant follows before it interprets a result. Ask the assistant to read it first. See methodology.

Example questions

• "Which accounts can you see?" leads to list_accounts.
• "What was our utilization over the last twelve months?" leads to get_utilization_trend.
• "Do we have the capacity for next quarter's planned hours?" leads to get_capacity_plan.
• "How has ABR trended for one client?" leads to get_abr_trend.
• "How accurate was our scoping on active projects?" leads to get_nonrecurring_scoping_accuracy and get_recurring_scoping_accuracy.
• "Show the financial overview for the latest month." leads to get_financial_overview.

Margins are always a share of AGI, never of billings. The assistant reads each result's caveats and freshness before it answers.