Cursor MCP: Connect Ken

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

1. 01

   Open Your Global MCP Config

   Create or open ~/.cursor/mcp.json to use Ken in every project. Use .cursor/mcp.json inside a project to scope Ken to that project.

2. 02

   Add Ken Under mcpServers

   Paste this entry and save the file. Cursor registers itself with Ken, so no client ID is needed.

   {
     "mcpServers": {
       "ken": {
         "url": "https://mcp.ken.so/mcp"
       }
     }
   }

3. 03

   Connect and Sign In

   Open Customize in the Cursor sidebar, find ken in your MCP servers, make sure it is on, and select Connect. Your browser opens the Ken sign-in. Sign in with the account you use in the Ken app, then select Allow access on the Ken approval screen. You never paste a client ID or secret.

4. 04

   Ask Cursor's Agent

   Cursor uses Ken's tools when your request needs them and asks for approval before it runs an MCP tool.

In short Yes. Cursor can send your Ken API key as a Bearer token when a browser sign-in is not an option.

1. 01

   Use a Ken API Key Header Instead

   Create a key in the Ken app under Settings > Integrations > API Keys and set it as KEN_API_KEY in your environment. Cursor fills ${env:KEN_API_KEY} from it, so the key stays out of mcp.json.

   {
     "mcpServers": {
       "ken": {
         "url": "https://mcp.ken.so/mcp",
         "headers": {
           "Authorization": "Bearer ${env:KEN_API_KEY}"
         }
       }
     }
   }

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.