---
title: "Connect Kenso to Zed with MCP"
description: "Add Kenso's remote MCP server to Zed with OAuth or an API key: exact steps checked against the vendor's docs, example prompts and fixes."
path: /mcp/zed
family: mcp
updated: 2026-10-17
html: /mcp/zed
sources:
  - "https://zed.dev/docs/ai/mcp"
facts:
  client: "Zed by Zed Industries"
  transport: "Remote HTTP"
  auth: "OAuth sign-in, or an API key in headers"
  server_url: "https://mcp.ken.so/mcp"
  client_plan_needed: "Not tied to a plan in Zed's docs"
  platforms: "Zed editor on macOS, Linux and Windows"
---

# Connect Kenso to Zed 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.

Zed connects to Kenso's remote MCP server from Settings > AI > MCP Servers. Choose Add Server, then Add Remote Server, and enter Kenso's server URL. With no Authorization header set, Zed prompts you to sign in to Kenso with OAuth.

## How Do You Connect Kenso to Zed?

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

1. **Open MCP Servers Settings**: Go to Settings > AI > MCP Servers, or run the agent: open settings action and select MCP Servers.
2. **Add Kenso as a Remote Server**: Select Add Server in the page header, then Add Remote Server. Name it kenso and enter the URL below. An entry you already added as ken keeps working: the name is only a label on your machine.

   ```
   https://mcp.ken.so/mcp
   ```
3. **Sign In to Kenso**: Leave out any Authorization header so Zed uses OAuth. Zed prompts you to authenticate. 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.
4. **Check the Status Dot**: Back in MCP Servers, the dot next to kenso turns green and its tooltip says Server is active.

## Can You Use a Kenso API Key Instead of OAuth?

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

1. **Use a Kenso API Key Header Instead**: Create a key in the Kenso app under Settings > Integrations > API Keys. Run zed: open settings file and add Kenso under context_servers with the header. With an Authorization header set, Zed skips the OAuth prompt.

   ```
   "context_servers": {
     "kenso": {
       "url": "https://mcp.ken.so/mcp",
       "headers": {
         "Authorization": "Bearer <KENSO_API_KEY>"
       }
     }
   }
   ```

## What Can You Ask Kenso From Zed?

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

**Example requests in Zed 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 many emails a day can this campaign send with the inboxes it has? | campaign_flow_read | Estimates how many emails a campaign can send with its inboxes. |
| 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. |

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 Zed?

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

**Common Zed connection problems and fixes**

| Problem | Fix |
| --- | --- |
| The dot next to kenso is not green | Hover the dot to read the status, and check the error Zed shows in the agent's response when a Kenso tool fails. |
| Zed never asks you to sign in to Kenso | Zed only starts OAuth when the server has no Authorization header. Remove the headers entry from kenso, or keep it and use a valid Kenso API key. |
| 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 answers 401 with an API key | The key was revoked or mistyped. Create a new one in the Kenso app under Settings > Integrations > API Keys. |

## Frequently Asked Questions

### Does Zed ask before it runs a Kenso tool?

Yes by default. In Zed v0.224.0 and later, agent.tool_permissions.default is confirm, which prompts before any tool runs, MCP tools included.

### Why does the agent ignore Kenso's tools?

How well MCP tools get called depends on the model. Mention Kenso by name in your request to point the agent at Kenso's tools.

### Which MCP features does Zed support?

Tools and Prompts. Kenso's search, campaign, inbox and analytics actions are all tools, so they work in Zed.

### Which Kenso workspace does Zed 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 |
| --- | --- | --- |
| Zed docs: Model Context Protocol | https://zed.dev/docs/ai/mcp | 2026-10-17 |

## Changelog

- 2026-10-17: Page published.
