Capabilities & limits

The MCP exposes a curated subset of the tour model. Knowing the boundary up front saves you from asking for something it can't do yet. Your agent knows this list too — it can call get_capabilities to answer accurately instead of guessing.

Available now

  • List your tours and read a tour's full editable state (settings + steps)
  • Create unpublished tours with ordered steps
  • Tooltip steps (anchored to a CSS selector) and modal steps (centered card, no selector)
  • Edit a tour's name and behavior settings: navigation buttons, button labels, progress counter, keyboard control, overlay-click behavior, highlight padding, and auto-navigate-to-next-page
  • Edit a tour's visibility: audience targeting rules, page URL pattern, minimum screen width, show-once frequency, and trigger (auto-play on page load vs manual)
  • Edit, add, delete, and reorder steps — title, body, target selector, type, position, backdrop, page URL pattern, plus per-step button labels/visibility, progress, and alignment
  • Check integration status and install the embed into your codebase
  • Verify the embed is live and whitelist your production domain

Editing tours

Your agent can change a tour after it's built — no need to re-create it. The typical flow:

  1. list_tours — find the tour you mean.
  2. get_tour — read its current settings and steps (each with its id).
  3. Make changes with update_tour_config (name + behavior settings), update_tour_visibility (targeting / URL pattern / screen width / frequency / trigger — send the complete value, it replaces rather than merges), update_step (a step's content/behavior — keeps the step's id and its analytics), add_step, delete_step, and reorder_steps.

Edits land on the unpublished tour, just like creation — you still review and publish from the dashboard.

Not supported yet

These are on the roadmap, not available today — the agent should tell you so rather than invent a workaround:

  • Set a tour's theme/colors or per-step visual styling
  • Per-step media/images (uploading requires the dashboard)
  • Create hints or announcements (including their visibility rules)
  • Read analytics

Excluded by design

  • Publishing a tour — always a deliberate action in the dashboard, so nothing the agent writes goes live without your review.
  • Creating your account or project from scratch — mint a token in the dashboard first; the agent works within a project you already own.

Try asking

  • "Set up StepsKit in this project and build a 3-step onboarding tour for the dashboard. Install the embed if it isn't already, then infer the target selectors from the code."
  • "Create a welcome tour: a modal intro, then tooltips pointing at the New Project button and the search bar."
  • "Open my Welcome tour and tighten the copy on every step, then rename the Next button to 'Continue'."
  • "Only show my Welcome tour to visitors on the Pro plan, and only on the /dashboard page."
  • "Add a final 'You're all set' modal step to the onboarding tour and move it to the end."
  • "What can the StepsKit MCP do right now? Can you publish a tour or set its theme?"