Ask your AI where users drop off after the click.

1. 1

   Create your Soku workspace

   The connection is public and identical for everyone — your Soku sign-in is what points it at your data. Connect one account in that workspace too: that is what your AI reads. The first time your AI uses the connection, Soku asks you to approve the access and names the workspace it will read through — so the workspace has to exist by then.

   Create your workspace

   Already have one? Nothing to do here — sign in when the connection asks for it.

2. 2

   Copy the Soku MCP connection

   https://api.soku.ai/mcp
3. 3

   Add it to Claude Code

   claude mcp add --transport http soku https://api.soku.ai/mcp

   1. Run the command in any project. It writes the configuration and prints an `Added …` line.
   2. Authorize separately — adding a server does not open a browser.
   3. Run `claude mcp list` to confirm the server reads `✔ Connected`.
4. 4

   Approve the access, then ask it something

   1. Inside Claude Code, run `/mcp` and follow the browser flow — or, from your shell, `claude mcp login soku`.
   2. The Soku consent page names the host, the workspace the grant will read through, and what the connection will be able to do.
   3. Approving creates the grant listed above on this page. Cancelling creates nothing.
   4. On a machine with no browser (SSH, headless Linux), `claude mcp login soku --no-browser` prints the URL and takes the pasted callback.

   Paste this first

   Using Soku, search for what capabilities I can reach.

   A list of capabilities with names, what each reads and what each costs. An empty list means the search matched nothing — try broader words. An error naming authorization means the host never completed the browser step.

Checked 2026-08-25 against Claude Code documentation. Menu names change between releases — look for connectors, apps, tools or integrations.