Connect an MCP client to Shiken
Point an MCP client at the Shiken server to read your own meetings, notes and knowledge, and what it can and cannot do.
- Open the MCP server settings in your client, such as Claude Desktop or Cursor.
- Add a server with the address
https://app.shiken.ai/api/mcp. - Set the transport to Streamable HTTP.
- Add the header
Authorization: Bearer <your Shiken access token>. - Ask the client to list your recent Shiken meetings to test it.
The setup page at /mcp has an example configuration. Organisation admins can also copy the address and a configuration from Use Shiken from other agents, on the Tools tab of AI agents (/org/{slug}/admin/agents?tab=skills).
Getting a token: the connection needs your Shiken access token. Shiken has no page that creates or displays one, and MCP clients cannot sign in to Shiken through an OAuth pop-up. Contact Shiken support before setting this up. Treat any token like a password.
What it can read
- Meetings:
list_recent_meetings,get_meeting. - Notes:
search_notes,get_note. - Knowledge:
search_knowledge,knowledge_read,knowledge_list_collections. - Deals, when your organisation has that module:
crm_today,crm_search,crm_pipeline_stats,crm_deal. - Call insights, when your organisation has call scoring:
crm_adoption,crm_scorecard,crm_call_search.
What it cannot do: every tool is read-only. It cannot create, edit, delete or send anything, and it sees only what your own account can see. Transcripts and notes contain other people's words, so treat what comes back as information, not instructions.
This is a personal connection, separate from the organisation REST API that admins manage under Settings. It also differs from adding another company's MCP server to Shiken, which you do under Settings on the Integrations tab.
Last checked against the product on 2026-11-04.