---
title: "Connect Kenso to Claude Desktop with MCP"
description: "Add Kenso's remote MCP server to Claude Desktop with OAuth or an API key: exact steps checked against the vendor's docs, example prompts and fixes."
path: /mcp/claude-desktop
family: mcp
updated: 2026-10-17
html: /mcp/claude-desktop
sources:
  - "https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp"
  - "https://modelcontextprotocol.io/docs/develop/connect-remote-servers"
  - "https://modelcontextprotocol.io/docs/develop/connect-local-servers"
facts:
  client: "Claude Desktop by Anthropic"
  transport: "Remote HTTP"
  auth: "OAuth sign-in, or an API key in Request headers"
  server_url: "https://mcp.ken.so/mcp"
  client_plan_needed: "Free (one custom connector), Pro, Max, Team or Enterprise"
  platforms: "macOS, Windows and Linux"
---

# Connect Kenso to Claude Desktop with MCP

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

Claude Desktop connects to Kenso's remote MCP server as a custom connector, not through claude_desktop_config.json. Add Kenso under Customize > Connectors, select Connect, then sign in to Kenso in your browser. It works on Free, Pro, Max, Team and Enterprise plans.

## How Do You Connect Kenso to Claude Desktop?

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

1. **Open Connectors in Claude Desktop**: In Claude Desktop, go to Customize > Connectors. Older guides, including the MCP docs, open the same page from Settings > Connectors.
2. **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
   ```
3. **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.
4. **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.
5. **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 Desktop can send your Kenso API key as a Bearer token when a browser sign-in is not an option.

1. **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. Do not add Kenso to claude_desktop_config.json: that file only starts local servers.

   ```
   Authorization: Bearer <KENSO_API_KEY>
   ```

## What Can You Ask Kenso From Claude Desktop?

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

**Example requests in Claude Desktop and the Kenso MCP tool that answers each one**

| Ask | Kenso tool used | What the tool does |
| --- | --- | --- |
| Find VPs of Sales at US software companies with 50 to 200 employees. | search_read | Searches 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_skill | Loads one Kenso workflow skill, such as create-campaign, into the chat. |
| Which of my campaigns are running right now? | campaigns_read | Lists campaigns and reads one campaign's settings and status. |
| How did my campaigns do this week? Show sends, replies and bounces for each one. | analytics_read | Reads campaign performance, engagement, deliverability and reply classifications. |
| Show me the replies that came in today and summarize each one. | threads_read | Lists inbox threads and reads their messages. |
| Pause the fintech campaign while I rewrite step 2. | campaigns_write | Creates, updates, launches, pauses and resumes campaigns. |

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.

- [Kenso MCP security](/mcp/security): Prompt injection, the read-only URL and what each role can change

## What If Kenso Does Not Connect in Claude Desktop?

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

**Common Claude Desktop connection problems and fixes**

| Problem | Fix |
| --- | --- |
| Kenso added to claude_desktop_config.json does not start | That file only launches local servers with a command. Remove the entry, restart Claude Desktop, and add Kenso under Customize > Connectors instead. |
| Kenso does not answer in a chat | Select + at the lower left of the chat, open Connectors and switch Kenso on for that conversation. |
| You need to change the URL or the key | Claude 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. |

## Frequently Asked Questions

### Do I edit claude_desktop_config.json to add Kenso?

No. That file configures local servers that Claude Desktop starts on your computer. Kenso is a remote server, so you add it as a custom connector in Settings.

### Is Kenso in Claude Desktop the same connector as on claude.ai?

Yes. Claude configures remote connectors through your Claude account, even in apps that run on your computer, so Kenso added on claude.ai is the connector Claude Desktop uses.

### Which Claude plans can add Kenso?

Free, Pro, Max, Team and Enterprise. Free allows one custom connector. On Team, only Owners and Primary Owners add connectors for the organization.

### Which Kenso workspace does Claude Desktop use?

With one workspace, Kenso picks it for you. If you belong to several, say which workspace you mean in your request, or add ?workspace= and the workspace id to the server URL to keep the connection in one. An API key that reaches several workspaces needs that. Kenso rejects calls to workspaces you are not a member of.

## Related

- [Kenso MCP server](/mcp): What Kenso's MCP server does and every client it works with
- [Claude MCP: Connect Kenso as a Custom Connector](/mcp/claude)
- [ChatGPT MCP: Connect Kenso as a Custom MCP Server](/mcp/chatgpt)
- [Claude Code MCP: Connect Kenso](/mcp/claude-code)
- [Cursor MCP: Connect Kenso](/mcp/cursor)
- [Codex MCP: Connect Kenso to OpenAI Codex](/mcp/codex)
- [Gemini CLI MCP: Connect Kenso](/mcp/gemini-cli)
- [Connect Kenso to Perplexity with MCP](/mcp/perplexity)
- [Connect Kenso to VS Code and GitHub Copilot with MCP](/mcp/vs-code)
- [Kenso pricing](/pricing): Plans and credit prices

## Sources

| Source | URL | Checked |
| --- | --- | --- |
| Claude Help Center: custom connectors using remote MCP | https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp | 2026-10-17 |
| MCP docs: connect to remote MCP servers | https://modelcontextprotocol.io/docs/develop/connect-remote-servers | 2026-10-17 |
| MCP docs: connect to local MCP servers | https://modelcontextprotocol.io/docs/develop/connect-local-servers | 2026-10-17 |

## Changelog

- 2026-10-17: Page published.
