---
title: "Connect Ken to Cline with MCP"
description: "Add Ken'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 Ken to Cline with MCP

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

## How Do You Connect Ken to Cline?

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

1. **Create a Ken API Key**: In the Ken 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 Ken 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.

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

## What Can You Ask Ken From Cline?

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

**Example requests in Cline and the Ken MCP tool that answers each one**

| Ask | Ken tool used | What the tool does |
| --- | --- | --- |
| Find VPs of Sales at US software companies with 50 to 200 employees. | search_read | Searches Ken's people and company database and returns filter facets. |
| Load Ken's campaign-planning skill and plan a 3-step cold email campaign for that list. | load_skill | Loads one Ken workflow skill, such as campaign-planning, 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. View-only members get read tools plus inbox replies.

## What If Ken 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 |
| --- | --- |
| Ken connects over SSE and fails | Add "type": "streamableHttp" to the ken entry. Cline treats an entry without a type as legacy SSE. |
| Ken'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. |
| Ken answers 401 with an API key | The key was revoked or mistyped. Create a new one in the Ken app under Settings > Integrations > API Keys. |

## Frequently Asked Questions

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

The Cline CLI can. Run cline mcp add ken 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 Ken from the Cline CLI with a key?

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

### Should I auto-approve Ken'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 Ken workspace?

Only what your Ken role allows. Admins and members get read and write tools, including campaign launches. View-only members get read tools plus inbox replies. Ken checks your role on every call, so a role change applies right away.

## Related

- [Ken MCP server](/mcp): What Ken's MCP server does and every client it works with
- [Claude MCP: Connect Ken as a Custom Connector](/mcp/claude)
- [ChatGPT MCP: Connect Ken as a Custom MCP Server](/mcp/chatgpt)
- [Claude Code MCP: Connect Ken](/mcp/claude-code)
- [Cursor MCP: Connect Ken](/mcp/cursor)
- [Codex MCP: Connect Ken to OpenAI Codex](/mcp/codex)
- [Gemini CLI MCP: Connect Ken](/mcp/gemini-cli)
- [Connect Ken to Perplexity with MCP](/mcp/perplexity)
- [Connect Ken to VS Code and GitHub Copilot with MCP](/mcp/vs-code)
- [Ken 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.