Clew MCP server: manage product tours from Claude, Cursor and ChatGPT

Step by step

1. Step 01

   Create a personal token in Clew

   Open Admin → AI access (MCP). Name the token after where it will live (“Claude on my laptop”), pick the access — Read only or Read and write — limit it to one site or leave All sites, and choose when it expires: 7, 30, 90 or 365 days, or never. Click Create token.

   The token is shown once: Clew keeps only a salted hash. Copy it now; the screen has already filled it into the client configs below the form.

   A token acts as the person who created it and never more: a viewer’s token can only read, and if your role changes, the token follows. On the Free plan the screen explains which plan includes the MCP server instead of the form.

   

2. Step 02

   Connect your assistant

   The server lives at https://tryclew.io/mcp and takes the token in the Authorization header. In Claude Code it is one command:

   claude mcp add --transport http clew https://tryclew.io/mcp \
     --header "Authorization: Bearer YOUR_TOKEN"

   Copy

   Run claude mcp list: clew … ✓ Connected means the token works. Cursor, Claude Desktop and Codex are just below in Set up in other clients, and the admin screen shows the same configs with your token already in them.

   

3. Step 03

   Ask for a tour in plain words

   Describe the page and the goal. The assistant reads how Clew works (the server ships its docs as MCP resources), checks your sites and existing tours so it doesn’t duplicate one, turns the HTML you paste into selectors and creates the tour.

   Build an onboarding tour for https://app.example.com/projects.
   Goal: a new user creates their first project.
   Use [data-tour] selectors, keep it to 4 steps, save it as a draft and show me.

   Copy

   Everything the assistant creates is a draft: visitors see nothing yet. Most clients also offer the server’s two prompts, Build an onboarding tour for my page and Find and fix broken tour steps, as ready-made commands.

   

4. Step 04

   Review the draft, then publish

   The reply links to the tour in the admin. Open it in the editor, preview it on your page, adjust the copy if you like — or keep going in the chat. When it looks right, say “publish it”: the assistant calls publish_tour. Plan limits apply exactly as in the admin: past the published-tour limit the answer is plan_limit_tours, the same refusal the admin shows.

   Editing a published tour from the chat changes what visitors see right away, and the assistant is told to warn you before it does.

   

5. Step 05

   Ask about results and broken steps

   “How is the onboarding tour doing?” returns viewers, completion and dismiss rates, drop-off per step and button clicks for the window you ask about, within your plan’s analytics history. While an A/B test runs, the answer includes both arms, the p-value and a verdict.

   “Fix broken steps” finds steps whose element was not found on real visits — with the selector and when it was last missed — and, after you paste the element’s new HTML, updates the selector.

   

6. Step 06

   Check what the assistant did

   Every change made over MCP lands in Audit log under the person and the token: anna@acme.io via MCP (Claude on laptop). Revoke a token on the AI access screen and every assistant using it loses access on its next request.

   

Set up in other clients

{
  "mcpServers": {
    "clew": {
      "url": "https://tryclew.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

curl -o ~/clew-mcp-stdio.js https://tryclew.io/clew-mcp-stdio.js

# claude_desktop_config.json
{
  "mcpServers": {
    "clew": {
      "command": "node",
      "args": ["/Users/you/clew-mcp-stdio.js"],
      "env": { "CLEW_MCP_TOKEN": "YOUR_TOKEN", "CLEW_MCP_URL": "https://tryclew.io/mcp" }
    }
  }
}

export CLEW_MCP_TOKEN=YOUR_TOKEN
codex mcp add clew --url https://tryclew.io/mcp --bearer-token-env-var CLEW_MCP_TOKEN

What the assistant can do

Security and limits

Troubleshooting and FAQ

Not installed yet? Pick a route