Features / AI Agents

Build tours with your AI coding agent

StepsKit ships an MCP server, so agents like Claude Code, Cursor, and Codex can install StepsKit and author product onboarding tours for your app — straight from your codebase.

{
  "mcpServers": {
    "stepskit": {
      "command": "npx",
      "args": ["-y", "@stepskit/mcp"],
      "env": { "STEPSKIT_TOKEN": "sk_live_..." }
    }
  }
}

Add this to your MCP client config, then ask your agent: "Set up StepsKit in this project and build an onboarding tour." Per-client setup (Claude Code, Cursor, Codex) →

Onboarding that starts where you build

Most onboarding tools assume you leave your editor, open a dashboard, and click through a builder. StepsKit can work that way too — but when your AI agent already understands your codebase, the fastest path to a live onboarding tour is to let the agent do the setup and the first draft.

The StepsKit MCP server gives your agent tools to check what it can do, read your integration state, install the embed, verify it, and author and edit tours — their steps, behavior, and visibility. Because the agent runs against your real components and selectors, the tours it drafts point at the right elements from the start.

What the agent does

  1. 1

    Reads your integration state

    The agent calls get_integration_status to see whether the StepsKit embed is installed, which domains are allowed, and how many tours already exist.

  2. 2

    Installs the embed for you

    Because the agent has your codebase on disk, it detects your framework (Next.js, Vite, plain HTML) and adds the embed snippet to the right file — you review the diff.

  3. 3

    Verifies the embed is live

    After you load a page once, verify_integration confirms the embed actually pinged StepsKit, so you know tours can render.

  4. 4

    Whitelists your production domain

    add_allowed_domain registers the domain your app ships on, so tours play in production (localhost is always allowed).

  5. 5

    Authors the tour — unpublished

    create_tour persists a tour from codebase context. It is created unpublished, so you review and publish it deliberately from the StepsKit dashboard.

The tools your agent gets

get_capabilities
Lists what the MCP can and can't do right now, so the agent gives accurate answers instead of promising something StepsKit can't do yet.
get_integration_status
Reads onboarding state — embed installed?, allowed domains, tour count — plus a ready-to-paste install snippet. The agent calls this first.
verify_integration
Confirms the embed has pinged StepsKit and is live after install.
add_allowed_domain
Whitelists a production domain so tours play there. localhost is always allowed.
create_tour
Authors an unpublished tour from codebase context. It never publishes — that stays a deliberate action in the dashboard.
list_tours & get_tour
Lists the project's tours and reads one tour's full editable state — settings, visibility, and steps with ids — so the agent can edit with context.
update_tour_config
Renames a tour and edits its behavior settings — navigation buttons, button labels, progress counter, keyboard control, overlay-click behavior, and highlight padding.
update_tour_visibility
Sets who sees the tour and when — audience targeting rules, page URL pattern, minimum screen width, show-once frequency, and trigger (auto-play on page load vs manual).
update_step, add_step, delete_step & reorder_steps
Edits, adds, removes, and reorders steps. Editing keeps a step's id and its analytics history, so the agent edits in place instead of rebuilding.

Frequently asked questions

Let your agent build the first tour

Create a free StepsKit project, add the MCP server to your agent, and ship an onboarding tour without leaving your editor.

Start Free