Connect Ken to goose with MCP

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

1. 01

   Start goose configure

   Run this in your terminal and choose Add Extension.

   goose configure

2. 02

   Pick the Remote Extension Type

   At What type of extension would you like to add, choose Remote Extension (Streamable HTTP). Call the extension ken.

3. 03

   Enter Ken's Endpoint

   At What is the Streamable HTTP endpoint URI, paste the URL below. Keep the default timeout of 300 seconds, add a short description, and answer No to custom headers.

   https://mcp.ken.so/mcp

4. 04

   Sign In to Ken

   goose registers itself with Ken and opens the Ken sign-in in your browser when it first connects. 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. goose 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. In goose configure, answer Yes to Would you like to add custom headers and add an Authorization header with the value Bearer and your key. In config.yaml, the extension entry looks like this.

   extensions:
     ken:
       name: ken
       type: streamable_http
       uri: https://mcp.ken.so/mcp
       headers:
         Authorization: "Bearer <KEN_API_KEY>"
       enabled: true
       timeout: 300

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.