@clikta/mcp-server
This MCP server lets Claude drive a real browser, record a flow with explanations, and generate/publish a Clikta interactive demo, guide, and video automatically.
Start a recording, launch Chromium, and optionally navigate to a
toolUrl.Navigate pages, click elements (with destructive-action confirmation guard), and fill fields while logging steps.
Add explanatory notes that feed Clikta's AI guide generator.
Capture ad-hoc screenshots into the Clikta screenshot library.
Finish a recording to generate/publish the guide and return a share link.
List existing recordings and Clikta tools to resume work, avoid duplicates, or attach recordings via
toolId.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@clikta/mcp-server Record a demo of the signup flow and generate a narrated video"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@clikta/mcp-server
MCP server that lets Claude drive a real browser and turn what it does into a Clikta interactive demo, step-by-step guide, and narrated video — automatically. No manual clicking, no Chrome extension required.
It reuses the exact same pipeline as the Clikta Chrome extension: every action is posted as an Event to your Clikta workspace, and clikta_finish_recording triggers the same AI guide generator that turns a human's recording into steps.
Built by Clikta — the design rationale and implementation history live in docs/mcp-architecture.md in the main clikta repo.
Requires a Pro or Team Clikta plan. A free-plan token gets a clear plan_required error from clikta_start_recording explaining that, rather than a bare auth failure.
Setup
Get an API token: in the Clikta web app, go to Settings → API Token and generate one (
clikta_...). This is the same token type the Chrome extension uses.Install Playwright's Chromium browser (runs automatically on
npm installviapostinstall, but you can re-run it manually):npx playwright install chromiumAdd the server to Claude Code (or any MCP host) — either via the CLI:
claude mcp add clikta -- npx -y @clikta/mcp-serveror by adding it to your
.mcp.json:{ "mcpServers": { "clikta": { "command": "npx", "args": ["-y", "@clikta/mcp-server"], "env": { "CLIKTA_API_URL": "https://clikta.com", "CLIKTA_API_TOKEN": "clikta_..." } } } }
Related MCP server: Glance
Environment variables
Variable | Required | Default | Description |
| yes | — | Generated in Settings → API Token |
| no |
| Point at a self-hosted instance if you run one |
| no |
| Set |
Tools
Tool | What it does |
| Creates a recording, launches the browser, optionally navigates to |
| Go to a URL, logs a |
| Click an element (by role/name, text, or CSS selector), logs a |
| Fill a field, logs an |
| Explain why you did something — feeds the AI guide generator the same way a human's spoken narration does. Use this liberally, it's the highest-leverage tool here |
| Ad-hoc screenshot saved to the Clikta screenshot library |
| Marks the recording done, generates the AI guide, publishes it, returns the share link, closes the browser |
| Lists existing recordings, to resume or avoid duplicates |
| Lists registered Clikta "Tool" entities (products), to attach a recording to an existing one via |
| Registers a new product/tool, so future recordings can attach to it via |
| Read-only summary of what Clikta already knows about a product: its modules/chapters, past recordings and their steps, pages visited before |
| Turns an objective into a short step outline before recording — pre-processing for a single demo |
| Proposes a MODULE — a set of 3-8 separate demos covering a broader goal — as a plan only, nothing saved |
| Persists a module and its planned chapters, once the user has approved the |
| Lists a product's modules, with chapter counts |
| Full per-chapter detail of one module — which chapters are recorded vs still pending, to resume across sessions |
Typical flow
For a single, self-contained demo:
clikta_list_tools/clikta_create_tool— find or register the productclikta_describe_toolandclikta_plan_demo— see what's already known, then plan the stepsclikta_start_recordingwith anameandtoolUrlpointing at the product/page to demoOpen the returned
watchUrlin a browser to watch steps land liveclikta_navigate/clikta_click/clikta_typethrough the flow, callingclikta_noteto explain intent along the wayclikta_finish_recordingto generate and publish the guide
For a broader goal that's really several demos (e.g. "document the whole onboarding experience"):
clikta_plan_moduleto propose a module (a name + 3-8 chapters) — show this to the user and get their explicit approval before continuing, this is the most important checkpoint in the whole flowclikta_create_moduleto persist it once approvedFor each chapter, follow the single-demo flow above, passing
moduleId/chapterIdtoclikta_start_recordingso the finished recording fills that slotclikta_get_moduleany time to check progress, including across separate sessions
The full server instructions (shown to the connecting client automatically) spell this out in more detail — see src/instructions.ts.
Guardrails
Never click through payments, deletions, or other irreversible actions without the user's explicit go-ahead —
clikta_clickblocks these by default (seesrc/locator.ts's destructive-label patterns) and requiresconfirm: trueto proceed.clikta_start_recordingwarns (non-blocking, via awarningfield in its result) whentoolUrl's host doesn't look like a staging/sandbox environment — prefer pointing it at one when available.API calls retry transient failures (network errors, 408/409/429/5xx) up to 3 times with backoff; real client errors (401/404/400/...) fail immediately since retrying won't help.
Screenshots may capture whatever is on the page, including sensitive data — same disclosure as the Chrome extension's privacy policy applies here.
Development
npm install
npm run build # tsc -> dist/
npm run dev # tsc --watchManual test scripts
Both spawn the built server and drive it through the real MCP client protocol (@modelcontextprotocol/sdk's Client + StdioClientTransport), not a shortcut import of the tool functions. Need a real Clikta instance and an API token — generate one from Settings → API Token in the Clikta web app (or, if you also have the main clikta repo checked out, node scripts/mint-api-token.mjs you@example.com there mints one directly against the dev DB without going through the login UI).
CLIKTA_API_URL=http://localhost:3000 CLIKTA_API_TOKEN=clikta_... node scripts/e2e-test.mjs # happy-path pipeline
CLIKTA_API_URL=http://localhost:3000 CLIKTA_API_TOKEN=clikta_... node scripts/guardrail-test.mjs # destructive-click block + sandbox warningAvailable Tools
9 toolsclikta_clickA
Click an element in the active recording's browser and log it as a step. Locate the element with role(+name), text, or selector — role/text are more resilient than raw CSS. Refuses to click elements that look destructive (delete, payment, purchase confirmation, unsubscribe, ...) unless confirm:true.
Inputs: name, role, text, confirm, +1 more.
clikta_finish_recordingA
Stop the active recording, generate the AI guide/demo from the captured steps, publish it, and return the shareable link. Closes the browser.
Inputs: no named parameters.
clikta_list_recordingsA
List existing recordings in the Clikta workspace, so you can resume or avoid duplicating work.
Inputs: no named parameters.
clikta_list_toolsA
List the products/tools already registered in the Clikta workspace (Clikta 'Tool' entities, e.g. 'Acme Dashboard'), so a new recording can be attached to an existing one via toolId instead of creating a duplicate.
Inputs: no named parameters.
clikta_noteA
Explain, in your own words, why you just did (or are about to do) something. This is the single most valuable tool here: notes feed the same mechanism as a human's spoken narration, and Clikta's AI guide generator uses them as context for writing each step's description. Call it liberally.
Inputs: text (required).
clikta_screenshotA
Take an ad-hoc screenshot of the current page and save it to the Clikta screenshot library (not tied to a recording step).
Inputs: title.
clikta_start_recordingA
Start a new Clikta recording. Creates the recording on the Clikta workspace, launches a real browser, and (if toolUrl is given) navigates there first. Call this before any other clikta_* action tool. Prefer a staging/sandbox toolUrl over production when one is available — the result includes a warning if the URL doesn't look like one.
Inputs: name (required), toolId, toolUrl, objective.
clikta_typeA
Fill a text field in the active recording's browser and log it as a step.
Inputs: value (required), name, role, text, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: navigation, recording control, interaction (click/type), annotation (note), capture (screenshot), and listing queries. There is no overlap or ambiguity between tool roles.
All tools follow a consistent snake_case pattern, with verbs like start, finish, click, type, list, and screenshot. The clikta_ prefix unifies the namespace, and naming is predictable across the entire set.
With 9 tools, the server is well-scoped for its purpose—recording browser sessions and generating guides. Each tool fills a necessary role in the workflow, with no clutter or redundancy.
The tool set covers the full lifecycle of creating a recording: start, navigate, interact, annotate, screenshot, and finish with publishing. Minor gaps exist, such as no update/delete for recordings, but these are not core to the stated purpose.
Related MCP Connectors
Make how-to videos, social clips and help articles from Claude or ChatGPT, and run your help center.
Let AI agents use your real, signed-in Chrome: tabs, clicks, forms, screenshots and video.
Let your AI agent operate any website through a real, logged-in browser session.
Make narrated tutorial videos of any website or web app by asking your AI assistant.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceLets Claude Code drive your own Chrome browser with human-like clicks, drags, and typing. It uses your real sessions and logins, and pauses for your confirmation on anything irreversible.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a real browser, so you can navigate, click, type, screenshot, and run multi-step test scenarios with assertions, visual regression, and console/network monitoring straight from the terminal.106 npmMIT
- AlicenseNot gradedqualityCmaintenanceLets Claude Desktop drive a real browser to execute plain-English goals as recorded walkthroughs, capturing HD video, per-step screenshots and a pass/fail action log. It also turns those recordings into written user guides, how-to articles and FAQs without any selectors or scripts to maintain.MIT
- AlicenseNot gradedqualityAmaintenanceGives Claude Code a real browser so it can navigate, click, type, screenshot, and assert against web pages directly from the terminal. Enables multi-step test scenarios, visual regression checks, session recording, and console/network error monitoring with security controls.106 npmMIT