---
title: "Connect Kenso to Cline with MCP"
description: "Add Kenso's remote MCP server to Cline with OAuth or an API key: exact steps checked against the vendor's docs, example prompts and fixes."
path: /mcp/cline
family: mcp
updated: 2026-10-17
html: /mcp/cline
sources:
  - "https://docs.cline.bot/mcp/connecting-to-a-remote-server"
  - "https://docs.cline.bot/mcp/mcp-overview"
  - "https://docs.cline.bot/cli/cli-reference"
facts:
  client: "Cline by Cline"
  transport: "Remote HTTP"
  auth: "API key header in the extension, OAuth in the Cline CLI"
  server_url: "https://mcp.ken.so/mcp"
  client_plan_needed: "Not tied to a plan in Cline's docs"
  platforms: "Cline extension for VS Code and other IDEs, plus the Cline CLI"
---

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

Cline connects to Kenso's remote MCP server over Streamable HTTP. Add Kenso as a remote server with type streamableHttp, Kenso's server URL and your Kenso API key as a Bearer header. The Cline CLI can sign in with OAuth instead.

## How Do You Connect Kenso to Cline?

**In short:** Add https://mcp.ken.so/mcp as a remote MCP server in Cline with your Kenso API key as a Bearer header.

1. **Create a Kenso API Key**: In the Kenso app, go to Settings > Integrations > API Keys and create a key for Cline.
2. **Open Cline's MCP Settings**: Select the MCP Servers icon in the top toolbar of the Cline panel, open the Configure tab, then select Configure MCP Servers to open cline_mcp_settings.json.
3. **Add Kenso as a Streamable HTTP Server**: Paste this entry under mcpServers with your key and save. Set type to streamableHttp: without it, Cline falls back to the legacy SSE transport. An entry you already added as ken keeps working: the name is only a label on your machine.

   ```
   {
     "mcpServers": {
       "kenso": {
         "type": "streamableHttp",
         "url": "https://mcp.ken.so/mcp",
         "headers": {
           "Authorization": "Bearer <KENSO_API_KEY>"
         },
         "disabled": false,
         "autoApprove": []
       }
     }
   }
   ```
4. **Check That Kenso's Tools Load**: Kenso appears in the MCP Servers list with its tools. Ask Cline something Kenso can answer to test it.

## What Can You Ask Kenso From Cline?

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

**Example requests in Cline 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. |
| Before I launch, preview who lands in the Series B segment. | segments_read | Previews which contacts land in a campaign segment. |
| 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. |

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

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

**Common Cline connection problems and fixes**

| Problem | Fix |
| --- | --- |
| Kenso connects over SSE and fails | Add "type": "streamableHttp" to the kenso entry. Cline treats an entry without a type as legacy SSE. |
| Kenso's tools time out | Raise the MCP timeout in Cline's MCP settings and try again. You can restart an unresponsive server from the same screen. |
| 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

### Can Cline sign in to Kenso with OAuth instead of an API key?

The Cline CLI can. Run cline mcp add kenso https://mcp.ken.so/mcp --transport http --yes, then run cline mcp and choose Authorize OAuth. Cline's docs do not describe OAuth for the IDE extension, so use an API key there.

### How do I add Kenso from the Cline CLI with a key?

Run cline mcp add kenso https://mcp.ken.so/mcp --transport http --header "Authorization: Bearer <KENSO_API_KEY>" --yes.

### Should I auto-approve Kenso's tools in Cline?

Only read tools such as search_read and campaigns_read. Leave write tools like campaigns_write out of autoApprove so Cline asks before it changes a campaign.

### What can Cline change in my Kenso workspace?

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.

## 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 |
| --- | --- | --- |
| Cline docs: connecting to a remote server | https://docs.cline.bot/mcp/connecting-to-a-remote-server | 2026-10-17 |
| Cline docs: MCP overview | https://docs.cline.bot/mcp/mcp-overview | 2026-10-17 |
| Cline docs: CLI reference | https://docs.cline.bot/cli/cli-reference | 2026-10-17 |

## Changelog

- 2026-10-17: Page published.
