StepTour speaks MCP — the Model Context Protocol used by assistants like Claude. Connect once, and your assistant can build, edit, translate, and organize interactive demos for you.
MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools. The StepTour MCP server exposes your workspace as a set of typed tools, authenticated with your personal API key.
That means you can say "build a tour of the new invoicing flow and translate it to German" — and the assistant creates the demo, writes the steps, and adds the translation, as drafts you review before publishing.
steptour_create_demo
Spin up a new demo with title, description, and player settings — created as a draft in your workspace.
steptour_record_flow
Drive a browser through a flow plan and capture every step with screenshots and highlights.
steptour_update_step
Add, rewrite, reorder, or delete steps — including tooltip text, media, and step types.
steptour_translate_demo
Create independent language versions of a demo, ready to fine-tune per market.
steptour_create_playlist
Group demos into multi-chapter playlists and control the chapter order.
steptour_list_demos
List demos, read their steps and settings, and check status before making changes.
Generate a personal API key in your StepTour dashboard. It scopes what the assistant can reach, and you can revoke it anytime.
Register the StepTour MCP server in your assistant's MCP configuration with your API key. The StepTour tools appear automatically.
Describe the tour you want in plain language. The assistant builds it as a draft — you review, adjust, and publish.
MCP is an open standard that lets AI assistants use external tools. When you connect StepTour over MCP, your assistant gets a set of StepTour tools — creating demos, editing steps, translating, managing playlists — and can use them on your behalf while you stay in the conversation.
Any MCP-compatible assistant, including Claude (desktop and Claude Code). You add the StepTour MCP server to the assistant's MCP configuration together with your API key, and the tools appear automatically.
It can create demos, record complete flows, add, update, reorder and delete steps, translate demos, group demos into playlists, and list or inspect what is in your workspace. In short: everything needed to build and maintain a demo library from chat.
Access is scoped by your personal API key, which you create in the dashboard and can revoke at any time. New demos are created as drafts, so nothing reaches your audience until you review and publish it.
For recording your own product by hand, yes — the extension is the fastest way to capture clicks. The MCP connection shines for automation: bulk edits, translations, rebuilding demos when your UI changes, and keeping step text consistent. Get the Chrome extension →