Cursor MCP: Connect Kenso
Cursor connects to Kenso's remote MCP server in one click: open Add to Cursor on this page, confirm, and sign in to Kenso in your browser. Or add Kenso's server URL under mcpServers in ~/.cursor/mcp.json. A Kenso API key header also works.
Can You Add Kenso to Cursor in One Click?
In short: Yes. Open the link, confirm Kenso in Cursor, then sign in to Kenso in your browser.
- Add to Cursor: Cursor opens its install dialog with Kenso's server URL filled in. Select Install, then Connect.
How Do You Connect Kenso to Cursor?
In short: Add https://mcp.ken.so/mcp as a remote MCP server in Cursor, then sign in to Kenso in your browser.
Open Your Global MCP Config
Create or open ~/.cursor/mcp.json to use Kenso in every project. Use .cursor/mcp.json inside a project to scope Kenso to that project.
Add Kenso Under mcpServers
Paste this entry and save the file. Cursor registers itself with Kenso, so no client ID is needed. An entry you already added as ken keeps working: the name is only a label on your machine.
{
"mcpServers": {
"kenso": {
"url": "https://mcp.ken.so/mcp"
}
}
}Connect and Sign In
Open Customize in the Cursor sidebar, find kenso in your MCP servers, make sure it is on, and select Connect. 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.
Ask Cursor's Agent
Cursor uses Kenso's tools when your request needs them and asks for approval before it runs an MCP tool.
Can You Use a Kenso API Key Instead of OAuth?
In short: Yes. Cursor 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 and set it as KENSO_API_KEY in your environment. Cursor fills ${env:KENSO_API_KEY} from it, so the key stays out of mcp.json.
{
"mcpServers": {
"kenso": {
"url": "https://mcp.ken.so/mcp",
"headers": {
"Authorization": "Bearer ${env:KENSO_API_KEY}"
}
}
}
}What Can You Ask Kenso From Cursor?
In short: Ask in plain language. The client picks the Kenso tool, and Kenso runs it with your workspace role.
| Ask | Kenso tool used | What the tool does |
|---|---|---|
| Find VPs of Sales at US software companies with 50 to 200 employees. | search_read | Searches 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_skill | Loads one Kenso workflow skill, such as create-campaign, into the chat. |
| Before I launch, preview who lands in the Series B segment. | segments_read | Previews which contacts land in a campaign segment. |
| How many emails a day can this campaign send with the inboxes it has? | campaign_flow_read | Estimates how many emails a campaign can send with its inboxes. |
| Which of my campaigns are running right now? | campaigns_read | Lists 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_read | Reads campaign performance, engagement, deliverability and reply classifications. |
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.
- Kenso MCP security: Prompt injection, the read-only URL and what each role can change
What If Kenso Does Not Connect in Cursor?
In short: Most failures come from a skipped sign-in step or a client setting.
| Problem | Fix |
|---|---|
| Kenso shows an error or no tools | Open the Output panel (Cmd+Shift+U on a Mac), pick MCP Logs from the dropdown and read the connection or auth error. |
| Another MCP server misbehaves next to Kenso | Switch servers off one at a time with their toggles in Customize to find the one that fails. A failing server does not stop the others. |
| Kenso worked, then asks you to sign in every time | The client's saved registration is gone. Remove Kenso and add it again so the client registers itself again. |
| Kenso answers 401 with an API key | The key was revoked or mistyped. Create a new one in the Kenso app under Settings > Integrations > API Keys. |
Frequently Asked Questions
~/.cursor/mcp.json makes Kenso available in every project. .cursor/mcp.json in a repo scopes it to that project and lets you commit it for your team, without any key in the file.
No. Cursor asks for approval before it uses MCP tools by default, so you see each Kenso call before it runs.
Yes. Cursor lets Enterprise admins set MCP policy and allowlist servers. Ask your admin to allow Kenso's server URL if Kenso does not appear.
With one workspace, Kenso picks it for you. If you belong to several, say which workspace you mean in your request, or add ?workspace= and the workspace id to the server URL to keep the connection in one. An API key that reaches several workspaces needs that. Kenso rejects calls to workspaces you are not a member of.
Related
Kenso MCP server
What Kenso's MCP server does and every client it works with
Claude MCP: Connect Kenso as a Custom Connector
ChatGPT MCP: Connect Kenso as a Custom MCP Server
Claude Code MCP: Connect Kenso
Codex MCP: Connect Kenso to OpenAI Codex
Gemini CLI MCP: Connect Kenso
Connect Kenso to Perplexity with MCP
Connect Kenso to VS Code and GitHub Copilot with MCP
Connect Kenso to Claude Desktop with MCP
Kenso pricing
Plans and credit prices
Sources
Changelog
- : Added the Add to Cursor link.
- : Page published.