Skip to Content
Clients

Connect Kenso to Perplexity with MCP

Perplexity adds Kenso's remote MCP server as a custom remote connector. Open Plugins, choose Add custom, add a remote MCP connector with OAuth and Streamable HTTP, then select the Kenso card to sign in. In an organization, an admin must allow custom connectors first.

View as MarkdownUpdated

How Do You Connect Kenso to Perplexity?

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

Open Plugins

Select Plugins in the Perplexity sidebar. If you do not see Plugins yet, open Customize > Connectors instead.

Add an MCP Connector

Choose Add custom > Connector > Add MCP connector, then select Remote.

Fill In the Kenso Server

Name it Kenso and paste the server URL below as the MCP Server URL. Set Authentication to OAuth and Transport to Streamable HTTP. Kenso supports dynamic client registration, so leave the client ID and secret empty.

https://mcp.ken.so/mcp

Add It and Sign In

Tick the box that acknowledges the risks of custom connectors and select Add. Then select the Kenso card on the Plugins page to start the sign-in. 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.

What Can You Ask Kenso From Perplexity?

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

Example requests in Perplexity 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.
Which fintech companies in Germany have more than 100 employees? Search Kenso's 250M people and 24M companies.search_readSearches Kenso's people and company database and returns filter facets.
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 Perplexity?

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

Common Perplexity connection problems and fixes
ProblemFix
The Kenso card shows an error tagPerplexity could not validate the server during setup. Open the card's menu, choose to modify it, and check that the URL is exactly the Kenso server URL with https.
You see no Plugins page or no Add custom optionPersonal accounts can use Customize > Connectors while Plugins rolls out. In an organization, ask an admin to turn on Allow members to add custom connectors, which is off by default.
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.

Frequently Asked Questions

Perplexity offers an API Key option for custom connectors, but its docs do not say how it sends the key. Use OAuth for Kenso, which Perplexity supports with dynamic client registration.

Perplexity's docs do not tie custom connectors to a plan for individual accounts. In an organization, an admin has to allow members to add custom connectors, and only admins can share a connector with everyone.

No. Perplexity says it does not verify third-party MCP servers, which is why it asks you to acknowledge the risk. Kenso's server is run by Kenso and only acts with the access you allow on the Kenso approval screen.

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