Categories › AI & Agents › Multi-agent, orchestration & workflows
Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.
Remote server: your requests and data go to app.stuntdouble.io. Claude Code: claude mcp add --transport http stunt-double https://app.stuntdouble.io/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_me — Get the account this connection is acting as: id, email, name, timezone and where notifications reach them. Use `timezone` when creating a slist_workspaces — List the workspaces you belong to, with your role in each. Call this first: almost every other tool needs a workspace_id from here.get_workspace — Get 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 glist_workspace_members — List the members of a workspace with their role, name and join date. Use it to resolve the user ids that runs, feedback and assignments carrsearch — Search everything in a workspace (projects, actors, checklists, interviews, automations, issues, goals, feedback, knowledge, insights, desiglist_projects — List the live projects in a workspace, most recently opened first. Call this after list_workspaces and match a target URL or product name agget_project — Get one project (the product tracked by checklists, workflows, interviews and feedback), including its URL, audience and product descriptioncreate_project — Create a project (a product to track with checklists, workflows, interviews and feedback). Call list_projects first and reuse a matching prolist_project_mcp_servers — List the third-party MCP servers attached to a project and the tools each allows. Configuration only: those tools are not callable here, butlist_workspace_guidelines — List the workspace's whole library of standing rules (design system, tone of voice, brand, compliance, accessibility, shared knowledge), witadd_workspace_guideline — Add a standing rule to the workspace library. Call list_workspace_guidelines first so you do not add a near-duplicate. Attach it to the projupdate_workspace_guideline — Update 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 remove_workspace_guideline — Remove a rule from the workspace library permanently. This detaches it from every project holding it, so prefer `update_workspace_guideline`list_project_guidelines — List the standing rules this project is held to: the workspace library rules it has attached. Read these before writing checks, interview guadd_project_guideline — Add a standing rule and hold this project to it (a design-system rule, a tone-of-voice rule, a compliance obligation, or shared knowledge). set_project_guideline — Attach 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 folist_actors — List active actors (persistent AI user personas) in a workspace, oldest first. Prefer reusing an existing actor over creating a new one; pasget_actor — Get an actor's details: description, system prompt, capabilities, and status. list_actor_knowledge has the knowledge it carries into runs.create_actor — Create an actor: a persistent AI user persona with its own browser, email inbox (for OTP and magic-link flows), and memory. The description update_actor — Update an actor's name, description, system prompt, kind, capabilities, or status. Only the fields you pass change; at least one is requiredlist_actor_knowledge — List 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 add_actor_knowledge — Add knowledge to an actor. Choose the kind: expertise for a skill or standard it judges by in every run (brand, tone of voice, design systemremove_actor_knowledge — Remove a knowledge entry from an actor permanently, so future runs no longer use it. Find the entry's id with list_actor_knowledge.list_conversations — List chat conversations with actors in a workspace, most recently active first, optionally filtered to one actor. Excludes the workspace assget_conversation — Get an actor conversation with its full message history, oldest message first. Find conversation ids with list_conversations.list_checklists — List the checklists in a workspace, with their target URL, actor, check count and a recent run. Check here before creating a new checklist: get_checklist — Get a checklist: its target URL, instructions, run settings, every check (with the `id` update_checklist needs to edit one in place) and itsget_checklist_run — Get a checklist run: per-check results with evidence, score, verdict and the change since the previous run. Poll after run_checklist every 3flag_check_verdict — Correct 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. Laterrun_checklist — Run a checklist (async): the actor drives a real browser through the product and judges each check, and may use the project's attached MCP screate_checklist — Create a browser checklist: an actor exercises the product at a URL and judges each check with evidence. Checks can verify flows ("a new useupdate_checklist — Update a checklist. Only the fields you pass change. Pass `checks` to replace the full set of checks, sending each existing check with the `delete_checklist — Delete a checklist and its checks and runs. This permanently discards run history; prefer update_checklist, or simply not running a checklislist_feedback — List the comments stakeholders and users have left on a project through the feedback widget, newest first. Each one is pinned to a page posiget_feedback — Get one feedback widget comment with its full reply thread, its page location and version, and a signed screenshot URL when one was capturedsummarise_feedback — Summarise a project's comments into themes ranked by severity, open questions, and a self-contained implementation brief for a coding agent.update_feedback_status — Update a feedback widget comment's status: "reviewed" once assessed, "resolved" when confirmed fixed (ideally after a checklist run proves ilist_workflows — List workflows (multi-step automations) in a workspace, newest first, with their triggers, whether each is active, its step count and its laget_workflow — Get a workflow with its steps, the edges connecting them, the order a run would reach them, and recent runs. Read this before editing steps:run_workflow — Trigger a workflow run now (async), whatever its trigger type: it executes the stored steps (see get_workflow), which can drive browsers, poNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.