MCP server

What the MCP server does

Finn runs a remote MCP server. Connect an AI assistant to it, such as Claude (web or desktop) or Claude Code, and the assistant can list and read your Finns, create new ones as drafts, and edit drafts on your behalf.

It's deliberately limited. No tool can place a call, start or stop a deployment, touch contacts or audiences, read transcripts or recordings, send messages, touch billing, delete anything, or take a Finn out of draft. To make a Finn live, deploy it from the dashboard.

Server


URL	`https://finn-mcp-73965536364.asia-southeast1.run.app/mcp`
Transport	Streamable HTTP. There's no package to install and nothing to run locally.
Auth	A personal MCP key: `finn_mcp_` followed by 48 hex characters

The key belongs to the person who generated it. Everything the assistant does happens as that person, in their organization. You can't pass an organization or creator ID to change that.

Get a key

In the dashboard, go to Settings → Integrations and find AI Assistants (MCP).
Click Generate key.
Enter a Key name, for example "work laptop". In Claude, the connector shows up under this name.
Click Generate.

The key is shown once. The dialog that shows it also gives you a ready-made connector link and Claude Code command. Copy what you need before you click Done, I've copied it.

The key list shows when each key was created and last used. Revoke stops a key on its next request. Finns already created with it aren't affected. There's no API for creating or revoking keys, and keys have no scopes: every key can use every tool below.

Connect a client

Claude (web or desktop)

The dialog's Claude app tab shows Your connector link:

https://finn-mcp-73965536364.asia-southeast1.run.app/mcp/finn_mcp_...

In Claude, open Customize → Connectors, click + and choose Add custom connector.
Paste the link as the remote MCP server URL and click Add.
In a new chat, open + → Connectors and switch Finn on.

The link contains your key, so anyone who has it can act as you. Treat it like a password, and revoke the key if it leaks.

On Claude's Free plan you can add one custom connector. On Team and Enterprise plans, only an Owner can add one, under Organization settings → Connectors, and everyone else then clicks Connect.

Claude Code

The dialog's Claude Code tab shows the command with your key filled in:

claude mcp add --transport http finn https://finn-mcp-73965536364.asia-southeast1.run.app/mcp \
  --header "Authorization: Bearer finn_mcp_..."

Run it in a terminal, then start claude.

Other clients

Any MCP client that supports streamable HTTP works. Point it at https://finn-mcp-73965536364.asia-southeast1.run.app/mcp and send Authorization: Bearer finn_mcp_....

To check the connection, ask the assistant to list your Finns. It should call list_finns.

Tools

There are thirteen.

Tool	Changes anything	What it does
`list_finns`	No	Your Finns, newest first: id, name, status, use case
`get_finn`	No	One Finn's persona and settings
`get_finn_variables`	No	The Finn's `{placeholders}`, `{{variables}}`, their CSV column mapping, and its post-call fields
`get_finn_stats`	No	Call totals, answer and success rates, minutes, cost and breakdowns for a date range. Defaults to the last 30 days. Aggregates only.
`summarize_finn_outcomes`	No	Totals for each post-call field over a date range: choice counts, number averages, common text answers. Aggregates only.
`list_orgs`	No	The organizations your key belongs to, and your role
`list_voices`	No	Voice IDs, filterable by a search term
`get_share_link`	Creates a link if there isn't one	The Finn's public share link
`create_finn`	Creates a draft	A new Finn from a name, identity, style and response guidelines, plus optional use case, language, voice and opening line
`generate_finn`	Creates a draft	A complete draft Finn from a plain-language brief, using the dashboard's AI Copilot. Takes up to a minute.
`duplicate_finn`	Creates a draft	A copy of a Finn. The call flow canvas, agent handbook, speech settings and share link aren't copied.
`update_finn_draft`	Edits a draft	Changes persona fields on a draft Finn. Fields you don't name keep their values.
`update_finn_variables`	Edits a draft	Maps `{placeholders}` to audience CSV columns, turns mapping on or off, and sets post-call fields

Tools that create or edit a Finn return a link to it in the dashboard. A dashboard tab that was already open won't list a new Finn until you reload it.

The edit tools only work on drafts. A Finn that has been deployed is edited in the dashboard.

The CSV column mapping that get_finn_variables and update_finn_variables read and write isn't applied on phone calls, and neither are single-brace {placeholders}. Calls fill {{ column }} variables in the welcome message and system prompt straight from the audience row. See variables.

get_share_link returns the existing link if there is one. If sharing was switched off or the link has expired, it says so rather than making a new one. Anyone with a share link can talk to the Finn in a browser, which uses your credits.

What the MCP can't do

Build or edit a call flow canvas, or attach tools. See workflow editor.
Place calls or create deployments. Use the dashboard, or the API: see api-calls and api-deployments.
Read individual calls, transcripts or recordings.
Notify the assistant when something happens. For events, use webhooks.

Troubleshooting

Symptom	Cause and fix
Every call fails with an auth error	The key was revoked or mistyped. Keys must be `finn_mcp_` plus 48 hex characters exactly. Generate a new one.
The Finn tools don't appear in Claude	The connector isn't switched on for this chat. Open + → Connectors and turn Finn on.
The assistant created a Finn you can't see	It's in the organization of the key's owner. Ask the assistant which account it used, and reload the dashboard.
An edit is refused	The Finn isn't a draft. Edit it in the dashboard.
A voice fails on a call	The voice ID was made up. Have the assistant call `list_voices` and pick one from the list.

API authentication: API keys for the REST API, which are separate from MCP keys
api-finns