Skip to Content
Clients

Connect Kenso to goose with MCP

goose connects to Kenso's remote MCP server as a Remote Extension (Streamable HTTP). Run goose configure, choose Add Extension, name it kenso and enter Kenso's server URL as the endpoint, then sign in to Kenso in your browser. A Kenso API key header also works.

View as MarkdownUpdated

How Do You Connect Kenso to goose?

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

Start goose configure

Run this in your terminal and choose Add Extension.

goose configure

Pick the Remote Extension Type

At What type of extension would you like to add, choose Remote Extension (Streamable HTTP). Call the extension kenso. An entry you already added as ken keeps working: the name is only a label on your machine.

Enter Kenso'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

Sign In to Kenso

goose registers itself with Kenso and opens the Kenso sign-in in your browser when it first connects. Your browser opens the Kenso sign-in. Sign in with the account you use in the Kenso app, then select Allow access on the Kenso approval screen. You never paste a client ID or secret.

Can You Use a Kenso API Key Instead of OAuth?

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

Use a Kenso API Key Header Instead

Create a key in the Kenso 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:
  kenso:
    name: kenso
    type: streamable_http
    uri: https://mcp.ken.so/mcp
    headers:
      Authorization: "Bearer <KENSO_API_KEY>"
    enabled: true
    timeout: 300

What Can You Ask Kenso From goose?

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

Example requests in goose and the Kenso MCP tool that answers each one
AskKenso tool usedWhat the tool does
Find VPs of Sales at US software companies with 50 to 200 employees.search_readSearches Kenso's people and company database and returns filter facets.
Load Kenso's create-campaign skill and plan a 3-step cold email campaign for that list.load_skillLoads one Kenso workflow skill, such as create-campaign, into the chat.
Which of my campaigns are running right now?campaigns_readLists 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_readReads campaign performance, engagement, deliverability and reply classifications.
Show me the replies that came in today and summarize each one.threads_readLists inbox threads and reads their messages.

Admins and members get read and write tools. A view-only seat gets read tools plus 20 write tools, inbox replies among them. Only the read-only URL, https://mcp.ken.so/mcp/readonly, removes every tool that writes.

What If Kenso Does Not Connect in goose?

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

Common goose connection problems and fixes
ProblemFix
The Kenso sign-in cannot reach goosegoose serves the OAuth callback on 127.0.0.1 with a random port. If a firewall or proxy blocks it, set GOOSE_OAUTH_CALLBACK_PORT to a fixed port you allow.
You cannot remove the Kenso extensiongoose only removes disabled extensions. Turn Kenso off first, then remove it.
A Kenso tool answers "Missing scope"Part of the Kenso approval screen was declined. Remove Kenso from the client, add it again and select Allow access.
Kenso answers 401 with an API keyThe key was revoked or mistyped. Create a new one in the Kenso app under Settings > Integrations > API Keys.

Frequently Asked Questions

Open the sidebar with the button at the top left, select Extensions, then Add custom extension. Choose the Remote Extension (Streamable HTTP) type and enter Kenso's server URL as the endpoint.

In goose's config.yaml, at ~/.config/goose/config.yaml on macOS, as an entry of type streamable_http with Kenso's URL as uri.

goose is an open source agent. Its docs say the project has moved to the Agentic AI Foundation (AAIF), which now publishes it.

Only what your Kenso role allows. Admins and members get read and write tools, including campaign launches. A view-only seat gets read tools plus 20 write tools: account_write, api_keys_write, calendar_write, claim_links_write, email_copy_write, integrations_write, ken_chats_write, meeting_notes_write, meeting_shares_write, notetaker_write, onboarding_write, permissions_write, provider_search_write, replies_write, saved_searches_write, scheduler_write, search_write, tags_write, threads_write and workspace_write. Of those, threads_write can send a reply email, delete threads and bulk-update them, scheduler_write can bulk-cancel bookings, meeting_shares_write can put the notes of a meeting the seat owns on a public link, provider_search_write spends the workspace's Blitz records, api_keys_write can revoke the seat's own API keys and connected agents, and workspace_write can create a new workspace. For a connection that cannot change anything, use https://mcp.ken.so/mcp/readonly. Kenso checks your role on every call, so a role change applies right away.

Sources

Changelog

  • : Page published.

On this page