Connect Ken to Cline with MCP

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. 01

   Create a Ken API Key

   In the Ken app, go to Settings > Integrations > API Keys and create a key for Cline.

2. 02

   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. 03

   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. 04

   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.

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

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