Connect Ken to Windsurf (Devin Desktop) with MCP

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

1. 01

   Open the MCP Config File

   Open ~/.config/devin/mcp_config.json, or %APPDATA%\devin\mcp_config.json on Windows. In the Cascade panel, the Open MCP config file icon in the MCPs section opens the same file.

2. 02

   Add Ken Under mcpServers

   Paste this entry and save. url is the key both the Cascade docs and the Devin CLI docs accept, and a URL defaults to Streamable HTTP.

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

3. 03

   Load Ken and Sign In

   In Cascade, press the refresh button in the MCPs section, then sign in when asked. In Devin Local, select Authenticate when Ken shows Needs auth in the MCP list. 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.

In short Yes. Windsurf 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 add it as a Bearer token in the headers object of the ken entry.

   {
     "mcpServers": {
       "ken": {
         "url": "https://mcp.ken.so/mcp",
         "headers": {
           "Authorization": "Bearer <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.