Claude MCP

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude call external tools. Finn runs an MCP server, so you can connect Claude to your Finn account and build voice agents by describing them in a conversation instead of filling in the builder by hand.

What this server does. It reads your Finns and creates or edits drafts. That is the whole surface. It cannot launch a Finn, dial a number, spend your balance, touch contacts or read transcripts — those stay in the dashboard, on purpose. The Scope section below says why.

Who this is for. Anyone who already uses Claude and would rather describe an agent than build it click by click. You do not need to write code. If you do not use Claude, you are not missing anything — the dashboard does everything this exposes, and more.

There are exactly two ways to connect, and you only need one:

Scope — what the server can and cannot do

This is deliberate, and it is enforced in two places — the server refuses to expose those tools, and the backend refuses the underlying requests even if something asks for them. The reason is the connector link described below: that link is itself a credential, so the worst a leaked one can do is read your Finns and edit your drafts. That is recoverable. "Call my customers and spend my balance" is not.

The consequence for you: Claude builds it, you launch it. Every Finn arrives as a draft, you review it in the dashboard, and you press the button.

Step 1 — Generate a key

In the dashboard: Settings → Integrations → AI Assistants (MCP) → Generate key.

The name you give the key is the name the connector shows up as inside Claude, so name it after wherever you plan to use it — "work laptop", "home desktop". Two keys then read as two distinguishable entries rather than two identical rows.

Your key looks like finn_mcp_ followed by a long string. It is shown exactly once. Copy what you need before you close the dialog; if you lose it, revoke the key and generate another.

A few things worth knowing about keys:

• A key carries your identity. A Finn created with your key lands in your organization, as you. If you use a colleague's key, the Finn appears in their account and you will not be able to find it.
• There are no scopes or tiers. Every key can do everything on the "Can" list above, and nothing on the "Cannot" list.
• Revoking is immediate. The server re-checks the key against your account on every single call, so a revoked key stops working on the next request — not at the end of some session.

Step 2 — Connect Claude

The dialog that shows your new key gives you both options, each as a single copy button. Pick the one that matches how you use Claude.

Option 1 — Claude app (claude.ai or Claude Desktop)

This is the one most people want. Nothing to install, nothing to edit.

Copy your connector link from the dialog. It looks like this, with your own key on the end:

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

Then, in Claude:

1. Open Customize → Connectors, click + and choose Add custom connector.
2. Paste the link as the remote MCP server URL, then click Add. It appears under your key's name.
3. In a new chat, open + → Connectors and switch Finn on, then ask Claude to create a Finn.

Two things to know about plans: the Free plan allows one custom connector, and on Team and Enterprise plans only an Owner can add one, from Organization settings → Connectors — everyone else then clicks Connect on it.

The trade-off: a custom connector is a single URL box with nowhere to put a password, so the link is the credential. Treat the whole URL the way you would treat your dashboard password — do not paste it into a chat, a ticket, a screenshot or a repo.

Option 2 — Claude Code (terminal)

Copy the command from the dialog. It is one line, so it pastes cleanly into bash, zsh, PowerShell and cmd alike:

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

1. Paste the command into a terminal and run it.
2. Run claude.
3. Ask it to create a Finn.

This form keeps the key in a header rather than in the URL, which is the safer of the two.

Other MCP clients

The server speaks streamable HTTP, not stdio, and it is stateless — there is no session to open or expire. Any client that supports an HTTP MCP endpoint works with either of the two doors above: the key in an Authorization: Bearer header against /mcp, or the key as the last path segment of /mcp/<key>.

claude_desktop_config.json is not one of the options. That file configures local MCP servers; the Finn server is remote, so it is added as a custom connector instead.

Step 3 — Check it worked

Ask Claude:

"What Finns do I have?"

A working connection answers with your actual Finn names. If Claude says it has no such tool, see Troubleshooting below.

The tools

Six tools, and Claude picks between them on its own — you never name one directly.

Building a Finn in conversation

Ask for what you want in plain language. The dialog offers this one as a starting point:

"Use the Finn connector to create a draft Finn called Maya that books appointments for a dental clinic: friendly, concise, English."

A fuller request looks like this:

"Create a Finn called Skylar that books 15-minute demo calls for our sales team. Warm and concise, never interrupts, always confirms the date and time back to the caller. It should only discuss demos and scheduling — if someone asks about pricing, offer to pass them to a human. Use a friendly female English voice."

To do that, Claude needs four things, and it will ask if you leave one out:

Optionally you can also give it a use-case label, a language, a voice, an opening line, and a custom vocabulary list for names it would otherwise mispronounce.

What comes back is a link to the new draft, its id, and which organization and account it landed in. From there:

1. Open the link and review it in the builder.
2. Ask Claude for changes — "make the opening line shorter", "add a branch for voicemail" — and it edits the draft in place.
3. When you are happy, attach a number and launch it in the dashboard. See Deployments.

A dashboard tab that was already open will not show the new Finn until you reload it.

Voices

Ask for a voice by description — "a calm male English voice" — and Claude will search the catalogue for you.

One thing to watch: new Finns are created on Cartesia, and a voice id from a different provider will save without complaint and then fail on a real call. If you ask for a specific provider, make sure it is the one your Finn actually uses. Voice Gallery has the full catalogue.

Security

The connector link is a password. On the one-link setup the key sits in the URL, so anyone who sees the URL has your access. Do not screenshot it, do not paste it into a shared chat, do not commit it.

Assume anything you paste is exposed. If a key has been in a chat window, a ticket or an email, revoke it and generate a new one. It costs nothing.

Revoke at Settings → Integrations → AI Assistants → Revoke. It takes effect on the next request. Finns already created are untouched — revoking a key does not delete anything it made.

One key per place. Separate keys for your laptop, your desktop and any colleague means you can revoke one without disturbing the others, and the connector name tells you which is which.

Check whose account you are in. If you are in more than one organization, ask Claude "which Finn organization am I in?" before creating anything. New Finns go to your most recently joined organization.

Troubleshooting

"Claude doesn't have any Finn tools"

• In the Claude app, open + → Connectors in the chat and check that Finn is switched on. Connectors are enabled per conversation.
• In Claude Code, restart it — it reads its MCP configuration at startup.
• On a Free plan, check you have not already used your one custom connector slot on something else.

"This connector link is not valid"

The key in the URL is malformed. It must be the whole thing, starting finn_mcp_, with nothing trimmed off the end and no trailing slash or space.

"This connector link has been revoked"

That key no longer exists. Generate a new one and update the connector.

"Could not reach the Finn backend to verify your key"

A transient problem on our side rather than anything wrong with your setup. Try again; if it persists, contact support.

Claude created a Finn but you cannot find it

Almost always the wrong account. Ask Claude "which organization was that created in?" — the answer names the organization and the email the key belongs to. If it is not yours, you are using someone else's key.

Claude says it cannot edit a Finn

It has been launched. The server only edits drafts; a live Finn is edited in the dashboard.

Next

• Creating a Finn → — the dashboard builder, and what each persona field does.
• Deployments → — attaching a number and taking a draft live.
• Voice Gallery → — the full voice catalogue.
• Integrations → — webhooks and the rest of the integration surface.