Skip to Content
Clients

Claude MCP: Connect Kenso as a Custom Connector

Claude connects to Kenso's remote MCP server as a custom connector on Free, Pro, Max, Team and Enterprise plans. Add Kenso under Customize > Connectors, select Connect, then sign in to Kenso and allow access. Free accounts get one custom connector.

View as MarkdownUpdated

How Do You Connect Kenso to Claude?

In short: Add https://mcp.ken.so/mcp as a remote MCP server in Claude, then sign in to Kenso in your browser.

Open Connectors

In Claude, go to Customize > Connectors. On a Team or Enterprise plan, an Owner adds Kenso once under Organization settings > Connectors (Add, then Custom, then Web), and each member then selects Connect on it.

Add a Custom Connector

Select + Add, then Add custom connector. Name it Kenso, paste the server URL below, then select Continue.

https://mcp.ken.so/mcp

Keep OAuth Sign-In

Claude detects that Kenso uses OAuth. If the form asks for an OAuth client, choose Register automatically, because Kenso registers each connector itself. Select Continue, then Add.

Connect and Sign In to Kenso

Select Connect on the Kenso connector. Your browser opens the Kenso sign-in. Sign in with the account you use in the Kenso app, then select Allow access on the Kenso approval screen. You never paste a client ID or secret.

Turn Kenso On in a Chat

In a chat, select + at the lower left, open Connectors and switch Kenso on for that conversation.

Can You Use a Kenso API Key Instead of OAuth?

In short: Yes. Claude can send your Kenso API key as a Bearer token when a browser sign-in is not an option.

Send a Kenso API Key as a Request Header

Create a key in the Kenso app under Settings > Integrations > API Keys. In the Add custom connector form, put it in Request headers as the Authorization header with the value Bearer and your key. On Team and Enterprise plans, everyone who uses that connector reaches Kenso with the same key, so prefer OAuth there.

Authorization: Bearer <KENSO_API_KEY>

What Can You Ask Kenso From Claude?

In short: Ask in plain language. The client picks the Kenso tool, and Kenso runs it with your workspace role.

Example requests in Claude and the Kenso MCP tool that answers each one
AskKenso tool usedWhat the tool does
Find VPs of Sales at US software companies with 50 to 200 employees.search_readSearches Kenso's people and company database and returns filter facets.
Which fintech companies in Germany have more than 100 employees? Search Kenso's 250M people and 24M companies.search_readSearches Kenso's people and company database and returns filter facets.
Load Kenso's create-campaign skill and plan a 3-step cold email campaign for that list.load_skillLoads one Kenso workflow skill, such as create-campaign, into the chat.
How did my campaigns do this week? Show sends, replies and bounces for each one.analytics_readReads campaign performance, engagement, deliverability and reply classifications.
Show me the replies that came in today and summarize each one.threads_readLists inbox threads and reads their messages.
Reply to that thread and propose two times next week.threads_writeReplies to an inbox thread.

Admins and members get read and write tools. A view-only seat gets read tools plus 20 write tools, inbox replies among them. Only the read-only URL, https://mcp.ken.so/mcp/readonly, removes every tool that writes.

What If Kenso Does Not Connect in Claude?

In short: Most failures come from a skipped sign-in step or a client setting.

Common Claude connection problems and fixes
ProblemFix
Kenso does not answer in a chatConnectors are switched on per conversation. Select + at the lower left of the chat, open Connectors and turn Kenso on.
You need to change the URL or the keyClaude has no edit option for connectors. Remove Kenso with the three dots next to it in Customize > Connectors, then add it again.
A Kenso tool answers "Missing scope"Part of the Kenso approval screen was declined. Remove Kenso from the client, add it again and select Allow access.
Kenso worked, then asks you to sign in every timeThe client's saved registration is gone. Remove Kenso and add it again so the client registers itself again.

Frequently Asked Questions

Yes. Claude Free allows one custom connector, so Kenso can be that one. Pro, Max, Team and Enterprise plans can add custom connectors too.

On Team, an Owner or Primary Owner adds it under Organization settings > Connectors. On Enterprise, a custom role with Manage access to Libraries can add it too. Members then select Connect and sign in with their own Kenso account.

Claude Desktop uses the same Customize > Connectors page. Claude Code loads claude.ai connectors when you sign in to Claude Code with a claude.ai subscription.

Only what your Kenso role allows. Admins and members get read and write tools, including campaign launches. A view-only seat gets read tools plus 20 write tools: account_write, api_keys_write, calendar_write, claim_links_write, email_copy_write, integrations_write, ken_chats_write, meeting_notes_write, meeting_shares_write, notetaker_write, onboarding_write, permissions_write, provider_search_write, replies_write, saved_searches_write, scheduler_write, search_write, tags_write, threads_write and workspace_write. Of those, threads_write can send a reply email, delete threads and bulk-update them, scheduler_write can bulk-cancel bookings, meeting_shares_write can put the notes of a meeting the seat owns on a public link, provider_search_write spends the workspace's Blitz records, api_keys_write can revoke the seat's own API keys and connected agents, and workspace_write can create a new workspace. For a connection that cannot change anything, use https://mcp.ken.so/mcp/readonly. Kenso checks your role on every call, so a role change applies right away.

Sources

Changelog

  • : Page published.

On this page