bots.st/stunt-double
Stunt Double
Run UX journey checks with AI personas
2398 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 69
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://app.stuntdouble.io/api/mcp
What it can do
| Tool | What it says it does |
|---|---|
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 system, compliance, accessibility), process for steps it follows, reference for facts it looks up when relevant (product docs, FAQs, policies), account for test… |
add_interview_item | Add a question or task to an interview section (create the section first with add_interview_section). Tasks are concrete jobs to attempt in the product ("Find the annual plan price and compare it with monthly"); questions probe comprehension and sentiment. Set expected_evidence on tasks so the… |
add_interview_participant | Attach a participant to an interview. Provide either actor_id (existing actor) or persona_spec (ad-hoc persona: name, bio, traits), not both. Vary personas and devices across participants (expertise, motivation, scepticism, mobile vs desktop) for richer findings, and use behaviour to dial… |
add_interview_section | Add a section to an interview’s discussion guide. Sections group related items (e.g. "First impressions", "Checkout"); add questions and tasks to it next with add_interview_item, using the returned id as section_id. |
add_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). Every checklist run, design review, interview and triage for the project is then held to it. The rule joins the workspace library, so check… |
add_workflow_step | Add a step to a workflow and connect it into the run. Only stores it: nothing executes until the workflow runs. Appends by default; `sort_order` splices it in at a position. In a run, run_checklist drives a real browser; notification emails or messages members on Slack; github_comment and… |
add_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 projects it applies to with `project_ids` here or `set_project_guideline` later, or set `apply_to_design_reviews` so every design review in the workspace is held… |
comment_on_pr | Post a comment on a GitHub pull request via the workspace GitHub connection. Use it to report checklist or interview results where engineers already look: a short verdict, then per-check outcomes with evidence highlights. Needs the Stunt Double GitHub App installed on the repository; call… |
connect_workflow_steps | Wire a step's output handle to another step, to build or repair a branch (adding and removing steps keeps the plain chain on their own). A condition's 'false' handle starts unconnected, so a failing condition ends the run. Connecting a connected handle replaces its edge; target_step_id: null… |
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 shapes who the persona is, so describe a person (background, goals, tech comfort), not a job title. Call list_actors first and reuse a matching actor… |
create_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 user can complete signup") or assert standards ("headlines use sentence case"), for brand, compliance and design-system audits. Any reachable URL works… |
create_interview | Create a user interview: AI persona participants complete tasks and answer questions against target_url, and results are synthesised into a report. target_url can be any reachable URL, including prototypes (Figma Make publish links, Claude design artifacts, v0) and preview deployments. Build the… |
create_project | Create 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. |
create_workflow | Create a workflow (multi-step automation) that runs checks without anyone asking. Triggers: manual, schedule (cron), webhook, or vercel_event / github_event / cursor_event / linear_event / slack_event / figma_event so checklists re-run on deploys, pull requests, or design updates. Add steps with… |
delete_checklist | Delete 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. |
delete_workflow | Delete a workflow and its steps and runs, and remove its schedule. This discards run history; prefer toggle_workflow to pause unless the user asks for deletion. |
flag_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. Later runs use it as calibration and re-record any code-run script; the run's own score is unchanged. Set clear to withdraw a correction. |
get_actor | Get an actor's details: description, system prompt, capabilities, and status. list_actor_knowledge has the knowledge it carries into runs. |
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 its 10 most recent runs. Call get_checklist_run with a run id for per-check results and evidence. |
get_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 30 to 60 seconds until `status` is terminal; `outcome` is the verdict on the experience. `comparison.changes` (what got better or worse) is usually the answer… |
get_conversation | Get an actor conversation with its full message history, oldest message first. Find conversation ids with list_conversations. |
get_feedback | Get 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. |
get_index_report | Get a site's Stunt Double Index report: how well AI agents (ChatGPT, Claude, Gemini and others) can find, understand and act on it. Returns the score out of 100, band, rank, category and provider scores, frictions, failing checks and when it was scored. A blocked or opted-out site has a null score… |
get_interview | Get an interview with its discussion guide (sections and their items, in order) and participants with their run status. Also useful for polling progress after launch_interview; call get_interview_report for the synthesised findings. |
get_interview_participant | Get an interview participant including their full transcript from the interview run. Use this for verbatim evidence behind a report finding. |
get_interview_report | Get an interview's synthesised report (summary, themes, recommendations, per-question rollup), plus `usability` (UMUX or UMUX-Lite scores when asked). Poll after launch_interview until report_status is completed or failed; report is null until generated. |
get_me | Get 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 runs and feedback from a teammate's in lists that carry only user ids. |
get_project | Get one project (the product tracked by checklists, workflows, interviews and feedback), including its URL, audience and product description. Archived projects read as not found. |
get_pull_request | Get details for a GitHub pull request (title, description, author, branches, change stats) via the workspace GitHub connection. Read it before writing a checklist for the change, then report back with comment_on_pr. |
get_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: `execution_order` is what actually runs, and any id in `unreachable_step_ids` is a step no run will ever reach. |
get_workflow_run | Get a workflow run with step-level details. Poll this after run_workflow until status is terminal (completed, failed or cancelled). |
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 grant: a network policy there applies on top of each worker's own, and a feature switched off there cannot be switched back on per project. |
launch_interview | Launch an interview round (async): every participant runs the discussion guide against the target URL in a real browser, and may call the allowed tools of MCP servers attached to the project (list_project_mcp_servers); then a report is synthesised. Requires at least one section with items and one… |
list_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 reads one when the task calls for it; reference and account entries are found by search. Check here before add_actor_knowledge to avoid duplicates; pass an… |
list_actors | List 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. |
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: re-running an existing one keeps its history as a regression signal. Use get_checklist for the checks themselves. |
list_conversations | List 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. |
list_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 position (often to a named element) and carries device info; filter by status "new" when triaging. Use summarise_feedback to turn a list of these into themes and… |
list_index_sessions | List the agent sessions behind a site's Index score: one AI provider attempting one benchmark task in a real browser, with status, score, rubric evidence, a summary and the frictions it hit. Defaults to the latest run (pass run_id for another); filter by provider or category. Use it to explain a… |
list_interviews | List the user interviews in a workspace, newest first, optionally filtered to one project. Returns summary rows; call get_interview for the discussion guide and participants, or get_interview_report for the findings. |
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 guides or design feedback for the project, and assert them as observable checks rather than restating them. `attachment_id` is this project's copy of the rule… |
list_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, but an actor in a run (checklist, interview, workflow) may call the allowed tools of servers whose in_force is true. Servers are registered and attached by… |
list_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 against these before creating anything new. |
list_pull_requests | List pull requests for a GitHub repository via the workspace GitHub connection, most recently created first (up to 30). Use it to find the PR number to pass to get_pull_request or comment_on_pr. |
list_workflows | List 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. |
list_workspace_guidelines | List 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 one that already exists with `set_project_guideline` beats typing a second copy… |
list_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 carry. |
list_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. |
regenerate_interview_report | Regenerate the synthesized report from existing participant transcripts (async), e.g. after adding participants. Returns the trigger run ID; poll get_interview_report until report_status is completed or failed. |
remove_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. |
remove_workflow_step | Remove a step and close the gap: whatever led into it is repointed at whatever it led to, so the rest of the automation still runs. |
remove_workspace_guideline | Remove 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. |
reorder_workflow_steps | Set the order a workflow runs its steps in, as one linear sequence. Pass every step id: a list that leaves a step out is refused, since that step would be disconnected from the run (remove it with remove_workflow_step instead). This rewires the whole automation, so a branch built on the canvas (a… |
request_index_rerun | Re-score a site on the Index after it ships changes for agents: fresh probes, then about 24 agent sessions over a few minutes. Owner only (whoever claimed it, a work email on that domain while unclaimed, or a platform admin), once every 10 minutes. Poll list_index_sessions with the run_id about… |
request_index_score | Add a site the Stunt Double Index does not track yet and give it a first score. Runs light HTTP probes (robots.txt, llms.txt, structured data, sitemaps) in under a minute; include_agent_sessions also starts live agent sessions, which may queue behind a shared daily budget. The site becomes public… |
run_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 servers (list_project_mcp_servers). Returns a run_id; poll get_checklist_run (runs take a few minutes). Counts against the workspace's plan and budget. Results… |
run_workflow | Trigger 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. Refused over the plan limit or budget cap. |
search | Search 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 listing and filtering, and before creating something that may already exist… |
search_index_domains | Search the Stunt Double Index for sites by domain or name, or browse the leaderboard. Results are ordered by overall score, highest first, with rank, sector and when each was last scored; sites the Index could not score come last with a null score and an unscored_reason. Omit query to read the top… |
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 for several projects without being retyped. `enabled: false` keeps the attachment but stands the rule down here, leaving every other project untouched. Safe to… |
And 9 more tools.
In its maker's words
Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.
- Website
- www.stuntdouble.io
- Source
- github.com/stunt-double/stuntdouble-mcp
- Publisher
- stuntdouble.io
- Listed from
- the official MCP Registry as
io.stuntdouble/mcp-server - Version
- 1.17.0, updated 4 Nov 2026
- Kinds of work
- Browser and automation, Images, video and audio, Search and research
The domain it lives on
- stuntdouble.io
- registered 18 Dec 2023 (2 years ago), at Cloudflare, Inc., its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2398 ms | |
| Answered | 2314 ms | |
| Answered | 1253 ms |
Next door
- Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, InstagramScrape and automate logged-in web data
- SkyelightPin feedback to rendered elements with code
- TapAutomate and validate logged-in browser tasks
- String Web AccessFetch URLs, crawl sites, search web, return clean Markdown
- ShipvoSimulate a phone and automate UI actions
Is this your bot? Claim its address to add a verified badge and keep the listing current.