Stunt Double
OnlineDeploy AI user personas to validate user journeys at scale. Find UX friction before real users do.
What it can do: 69 tools
get_meread-onlyGet the account this connection is acting as: id, email, name, timezone and where notifications reach them. Use `timezone` when creating a scheduled workflow rather than defaulting to UTC, and `id` to tell your own runslist_workspacesread-onlyList the workspaces you belong to, with your role in each. Call this first: almost every other tool needs a workspace_id from here.get_workspaceread-onlyGet workspace details by ID or slug, including the admin-set controls that decide what runs in it may do. `settings` is a ceiling, never a grant: a network policy there applies on top of each worker's own, and a featurelist_workspace_membersread-onlyList the members of a workspace with their role, name and join date. Use it to resolve the user ids that runs, feedback and assignments carry.searchread-onlySearch everything in a workspace (projects, actors, checklists, interviews, automations, issues, goals, feedback, knowledge, insights, design reviews, resources, conversations) by name or content. Use it instead of listilist_projectsread-onlyList the live projects in a workspace, most recently opened first. Call this after list_workspaces and match a target URL or product name against these before creating anything new.get_projectread-onlyGet one project (the product tracked by checklists, workflows, interviews and feedback), including its URL, audience and product description. Archived projects read as not found.create_projectCreate a project (a product to track with checklists, workflows, interviews and feedback). Call list_projects first and reuse a matching project rather than creating a duplicate.list_project_mcp_serversread-onlyList the third-party MCP servers attached to a project and the tools each allows. Configuration only: those tools are not callable here, but an actor in a run (checklist, interview, workflow) may call the allowed tools olist_workspace_guidelinesread-onlyList the workspace's whole library of standing rules (design system, tone of voice, brand, compliance, accessibility, shared knowledge), with how many projects hold each one. Read this before writing a rule: attaching onadd_workspace_guidelineAdd a standing rule to the workspace library. Call list_workspace_guidelines first so you do not add a near-duplicate. Attach it to the projects it applies to with `project_ids` here or `set_project_guideline` later, orupdate_workspace_guidelineUpdate a rule in the workspace library, or switch it off. Every project holding it is held to the new wording, so prefer editing the shared rule over adding a near-duplicate. Pass only the fields to change; at least oneremove_workspace_guidelineRemove a rule from the workspace library permanently. This detaches it from every project holding it, so prefer `update_workspace_guideline` with `enabled: false` when the rule may come back.list_project_guidelinesread-onlyList the standing rules this project is held to: the workspace library rules it has attached. Read these before writing checks, interview guides or design feedback for the project, and assert them as observable checks raadd_project_guidelineAdd a standing rule and hold this project to it (a design-system rule, a tone-of-voice rule, a compliance obligation, or shared knowledge). Every checklist run, design review, interview and triage for the project is thenset_project_guidelineAttach a library rule to a project, detach it, or switch it off for this project alone. Attaching is how one workspace rule comes to hold for several projects without being retyped. `enabled: false` keeps the attachmentlist_actorsread-onlyList active actors (persistent AI user personas) in a workspace, oldest first. Prefer reusing an existing actor over creating a new one; pass an id from here to get_actor, interviews and checklists.get_actorread-onlyGet an actor's details: description, system prompt, capabilities, and status. list_actor_knowledge has the knowledge it carries into runs.create_actorCreate an actor: a persistent AI user persona with its own browser, email inbox (for OTP and magic-link flows), and memory. The description shapes who the persona is, so describe a person (background, goals, tech comfortupdate_actorUpdate an actor's name, description, system prompt, kind, capabilities, or status. Only the fields you pass change; at least one is required. Set status to "archived" to soft-delete.list_actor_knowledgeread-onlyList what an actor knows, oldest first. Each entry has a kind: expertise and process entries are listed by title in every run and the actor reads one when the task calls for it; reference and account entries are found byadd_actor_knowledgeAdd knowledge to an actor. Choose the kind: expertise for a skill or standard it judges by in every run (brand, tone of voice, design system, compliance, accessibility), process for steps it follows, reference for factsremove_actor_knowledgeRemove a knowledge entry from an actor permanently, so future runs no longer use it. Find the entry's id with list_actor_knowledge.list_conversationsread-onlyList chat conversations with actors in a workspace, most recently active first, optionally filtered to one actor. Excludes the workspace assistant's conversations. Pass an id to get_conversation to read the messages.get_conversationread-onlyGet an actor conversation with its full message history, oldest message first. Find conversation ids with list_conversations.list_checklistsread-onlyList the checklists in a workspace, with their target URL, actor, check count and a recent run. Check here before creating a new checklist: re-running an existing one keeps its history as a regression signal. Use get_cheget_checklistread-onlyGet a checklist: its target URL, instructions, run settings, every check (with the `id` update_checklist needs to edit one in place) and its 10 most recent runs. Call get_checklist_run with a run id for per-check resultsget_checklist_runread-onlyGet a checklist run: per-check results with evidence, score, verdict and the change since the previous run. Poll after run_checklist every 30 to 60 seconds until `status` is terminal; `outcome` is the verdict on the expeflag_check_verdictCorrect a wrong passed or failed verdict on one check: pass the result_id from get_checklist_run and a note on what was actually true. Later runs use it as calibration and re-record any code-run script; the run's own scorun_checklistRun a checklist (async): the actor drives a real browser through the product and judges each check, and may use the project's attached MCP servers (list_project_mcp_servers). Returns a run_id; poll get_checklist_run (runcreate_checklistCreate a browser checklist: an actor exercises the product at a URL and judges each check with evidence. Checks can verify flows ("a new user can complete signup") or assert standards ("headlines use sentence case"), forupdate_checklistUpdate a checklist. Only the fields you pass change. Pass `checks` to replace the full set of checks, sending each existing check with the `id` from get_checklist so it keeps its run history. Changing the checks, instrucdelete_checklistDelete a checklist and its checks and runs. This permanently discards run history; prefer update_checklist, or simply not running a checklist, unless the user asks for deletion.list_feedbackread-onlyList the comments stakeholders and users have left on a project through the feedback widget, newest first. Each one is pinned to a page position (often to a named element) and carries device info; filter by status "new"get_feedbackread-onlyGet one feedback widget comment with its full reply thread, its page location and version, and a signed screenshot URL when one was captured. Find the id with list_feedback.summarise_feedbackSummarise a project's comments into themes ranked by severity, open questions, and a self-contained implementation brief for a coding agent. Read the brief before proposing changes instead of reasoning over raw comments.update_feedback_statusUpdate a feedback widget comment's status: "reviewed" once assessed, "resolved" when confirmed fixed (ideally after a checklist run proves it), "dismissed" sparingly. The dashboard reflects the change immediately.list_workflowsread-onlyList workflows (multi-step automations) in a workspace, newest first, with their triggers, whether each is active, its step count and its last run. Call get_workflow on one for its steps and the order a run takes them.get_workflowread-onlyGet a workflow with its steps, the edges connecting them, the order a run would reach them, and recent runs. Read this before editing steps: `execution_order` is what actually runs, and any id in `unreachable_step_ids` irun_workflowTrigger a workflow run now (async), whatever its trigger type: it executes the stored steps (see get_workflow), which can drive browsers, post PR comments and notify members. Returns a run ID; poll get_workflow_run. Refu
…and 29 more.
Connect it
claude mcp add --transport http stunt-double https://app.stuntdouble.io/api/mcpSettings → Connectors → Add custom connector
URL: https://app.stuntdouble.io/api/mcp{
"mcpServers": {
"stunt-double": {
"url": "https://app.stuntdouble.io/api/mcp"
}
}
}{
"servers": {
"stunt-double": {
"type": "http",
"url": "https://app.stuntdouble.io/api/mcp"
}
}
}Questions
What does Stunt Double do?
Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do. It exposes 69 tools to AI assistants.
What tools does Stunt Double provide?
69 tools, including get_me, list_workspaces, get_workspace, list_workspace_members, search, list_projects, get_project, create_project, list_project_mcp_servers, list_workspace_guidelines, add_workspace_guideline, update_workspace_guideline….
How do I connect Stunt Double to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://app.stuntdouble.io/api/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does Stunt Double require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is Stunt Double online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes Stunt Double?
stuntdouble.io. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Project Management
-
SanityOnline · sign-in requiredPopular
Gives AI agents direct access to your Sanity projects and guidance for working with them
-
LinearOnline · sign-in requiredOfficialPopular
Find and manage issues, projects, and documents in your Linear workspace.
-
ReqResOnlineOfficial
Hosted backend for AI agents: create projects with persistent collections and keys, no signup.
-
ChainstackOnlineOfficial
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
-
Singularity AppOnline · sign-in requiredOfficialNew
Manage tasks, projects, habits, Kanban boards, and time tracking with SingularityApp.
-
Release AlertOnlineOfficialNew
Connect AI assistants to Release Alert.