@clikta/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIKTA_API_URL | No | Base URL of the Clikta API. Point at a self-hosted instance if you run one. | https://clikta.com |
| CLIKTA_API_TOKEN | Yes | API token generated in Clikta web app (Settings → API Token). Required. | |
| CLIKTA_MCP_HEADLESS | No | Set to 'true' to run Chromium headless (CI/scripted use). Headed by default so you can watch the demo happen live. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| clikta_navigateA | Navigate the active recording's browser to a URL and log it as a step. |
| clikta_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. |
| clikta_typeA | Fill a text field in the active recording's browser and log it as a step. |
| 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. |
| 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). |
| 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. |
| clikta_list_recordingsA | List existing recordings in the Clikta workspace, so you can resume or avoid duplicating work. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.