Back to Browse

Stuntdouble MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.

About

Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.

Remote endpoints: streamable-http: https://app.stuntdouble.io/api/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-stuntdouble-mcp-server": {
      "url": "https://app.stuntdouble.io/api/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Stunt Double MCP Server

Deploy AI user personas to validate user journeys at scale. Find UX friction before real users do.

Stunt Double deploys AI agents with realistic user personas to validate user journeys at scale. Create actors, run automated workflows and checklists against any web app, and surface friction points before real users encounter them. Integrates with Claude, Linear, GitHub, and Slack.

This repository

This repo holds plugin and MCP configuration (.cursor-plugin/plugin.json, root mcp.json, server.json), plus skills, agents, and Cursor rules. There is no package.json and no runnable server here — the MCP endpoint is hosted at https://app.stuntdouble.io/api/mcp from the main Stunt Double codebase. See CONTRIBUTING.md for how to validate edits and avoid confusing this folder with a Node package.

Quick Start

Claude Code

claude mcp add --transport http stuntdouble https://app.stuntdouble.io/api/mcp

Claude Desktop

Go to Settings → Connectors → Add and paste:

https://app.stuntdouble.io/api/mcp

Cursor / Windsurf

Add the mcpServers block below to an MCP config file:

  • Project-local (recommended for this repo clone): .cursor/mcp.json at the root of your project.
  • Global (all projects): ~/.cursor/mcp.json on macOS/Linux (see Cursor MCP docs for your OS).
{
  "mcpServers": {
    "stuntdouble": {
      "url": "https://app.stuntdouble.io/api/mcp"
    }
  }
}

Use only url for remote servers (Streamable HTTP is negotiated automatically). Extra keys such as "type": "streamable-http" are not part of Cursor's documented mcp.json shape and can break plugin validation.

Cursor marketplace (one-click install) expects a plugin layout: .cursor-plugin/plugin.json plus root mcp.json. Those files are in this repo. The plugin logo path is assets/logo.png (bundled in this repository). The server.json file is the separate MCP registry manifest for mcp-publisher and directory listings; Cursor's installer does not use it.

Authentication

Authentication is handled automatically via OAuth 2.1 with PKCE. The first time your AI client connects, a browser window will open for you to sign in and authorise access to your Stunt Double account. No API keys or tokens required.

For Cursor, the OAuth redirect URI is fixed to cursor://anysphere.cursor-mcp/oauth/callback (docs).

Available Tools

Account

ToolDescription
get_meThe account this connection acts as: id, email, name, timezone, notification channel

Notification channel and timezone are account settings rather than workspace ones, so they are the same answer in every workspace. Pass the timezone when creating a scheduled workflow, or "every weekday at 9" becomes nine in UTC.

Workspaces

ToolDescription
list_workspacesList your workspaces
get_workspaceGet workspace details by ID or slug, including its admin-set controls (settings)
list_workspace_membersList members of a workspace

get_workspace reports the workspace security controls under settings: public sharing, the feedback widget, self-hosted workers, and the network policy. They are ceilings set by an admin, so a feature switched off there cannot be switched back on for a single project.

Search

ToolDescription
searchSearch a workspace across projects, actors, checklists, interviews, automations, issues, goals, feedback, actor knowledge, insights, design reviews, project resources and conversations. Ranked, with optional filters

search takes a workspace_id plus an optional query, types filter, project_id filter and limit (max 50). Terms are matched as prefixes, so a partial word is enough. Omit query to browse the most recently updated items. Results carry the id you need for the matching getter, so it is usually cheaper than listing an entity type and filtering the list yourself. Reach for it before creating anything, to find the actor or checklist that already covers the job.

Projects

ToolDescription
list_projectsList projects in a workspace
get_projectGet a project (the product tracked by checklists, workflows, feedback)
create_projectCreate a project (a product to track with checklists, workflows, feedback)
list_project_mcp_serversThe MCP servers this project's runs can reach

A project is archived, never deleted, and an archived project reads as missing from every tool here. Registering an MCP server and attaching it to a project are workspace-admin actions in the dashboard; list_project_mcp_servers is how you check what tools a run will actually have before writing a checklist that depends on one.

Guidelines

Standing rules the team holds the product to: design system, tone of voice, brand, content, accessibility, compliance, security, performance, or shared knowledge. A guideline is owned by the workspace and attached to the projects it applies to, so one rule can hold for every project without being retyped. Whatever is in force is rendered into every checklist run, design review, interview and triage for that project.

ToolDescription
list_workspace_guidelinesThe workspace library, with how many projects hold each rule
add_workspace_guidelineAdd a rule to the library, optionally attaching it to projects
update_workspace_guidelineEdit a rule, switch it off, or apply it to every design review in the workspace
remove_workspace_guidelineRemove a rule from the library, detaching it from every project
list_project_guidelinesThe rules this project is held to
add_project_guidelineRecord a rule and hold this project to it
set_project_guidelineAttach a library rule to a project, detach it, or switch it off there

Two switches decide whether a rule is in force for a project: the library's enabled and the attachment's. list_project_guidelines folds them into one enabled so you never have to reason about both. A rule with apply_to_design_reviews set also holds for design reviews raised from Slack or Linear, which carry no project to attach it through.

Codify a standard as a guideline rather than repeating it in each checklist, and search the library before writing a new rule: attaching the one that already exists keeps the team's standard in a single place to edit.

Actors

ToolDescription
list_actorsList active actors in a workspace
get_actorGet actor details including system prompt and capabilities
create_actorCreate a new actor in a workspace
update_actorUpdate actor name, description, system prompt, capabilities, or status. Set status to "archived" to soft-delete

Knowledge

ToolDescription
list_actor_knowledgeList knowledge entries for an actor
add_actor_knowledgeAdd a knowledge entry to an actor
remove_actor_knowledgeRemove a knowledge entry

Conversations

ToolDescription
list_conversationsList conversations, optionally filtered by actor
get_conversationGet a conversation with its messages

Checklists

ToolDescription
list_checklistsList checklists in a workspace
get_checklistGet checklist details, checks, and recent runs
get_checklist_runGet a checklist run with per-check results
run_checklistTrigger a checklist run (async). Returns run ID
create_checklistCreate a browser-based QA checklist (host via project or URL, actor, instructions, checks)
update_checklistUpdate a checklist (pass checks to replace the full set)
delete_checklistDelete a checklist and its checks and runs

Workflows

ToolDescription
list_workflowsList workflows in a workspace
get_workflowGet workflow details with steps and recent runs
run_workflowTrigger a workflow run (async). Returns run ID
get_workflow_runGet a workflow run with step-level details
create_workflowCreate a workflow (multi-step automation)
update_workflowUpdate a workflow's name, description, or trigger
toggle_workflowActivate or pause a workflow
delete_workflowDelete a workflow and its steps and runs
add_workflow_stepAppend a step to a workflow
update_workflow_stepUpdate a workflow step type, config, or sort order
remove_workflow_stepRemove a step from a workflow

Feedback

ToolDescription
list_feedbackList feedback for a project, newest first
get_feedbackGet a feedback submission with its replies
update_feedback_statusUpdate feedback status

GitHub

ToolDescription
list_pull_requestsList pull requests for a GitHub repository
get_pull_requestGet details for a GitHub pull request (title, author, branches, stats)
comment_on_prPost a comment on a GitHub pull request

Interviews

Structured user interviews — actors or generated personas run through a discussion guide (sections + questions/tasks) against a target URL, then Stunt Double synthesises themes and recommendations.

ToolDescription
list_interviewsList interviews in a workspace, optionally filtered by project
get_interviewGet an interview with its discussion guide (sections + items) and participants
create_interviewCreate a new interview in a project (name, target URL, research brief)
update_interviewUpdate an interview's name, target URL, research brief, or status
add_interview_sectionAdd a section to the discussion guide
add_interview_itemAdd a question or task to a section
add_interview_participantAttach a participant — either an existing actor or an ad-hoc persona_spec
get_interview_participantGet a participant including their full transcript from the run
get_interview_reportGet the current synthesised report (summary, themes, recommendations, per-question rollup)
launch_interviewLaunch the interview round (async). Returns the trigger run ID
regenerate_interview_reportRe-run synthesis on existing transcripts (async). Returns the trigger run ID

Prompts

Most MCP clients (Claude, Claude Code, Cursor) surface these as slash commands. Each is a self-contained recipe: which tools to call, in what order, and how to report back.

PromptDescription
validate_designValidate a live design, prototype, or preview URL (Figma Make, Claude artifact, v0, staging) with AI personas
verify_changeVerify a shipped or previewed code change by running an actor through the affected flows, optionally commenting on the PR
run_user_researchRun a structured multi-persona interview study and synthesise themes and recommendations
triage_feedbackTriage user feedback on a project: cluster it, reproduce issues with an actor, and update statuses
setup_guardrailsStand up checklists for critical flows plus a workflow that re-runs them on a schedule or on deploy/PR events
check_brandAudit a product against brand and tone-of-voice guidelines, flagging deviations with evidence
check_design_systemAudit a live product against its design system (typography, colour, spacing, components) on rendered pages
check_complianceCheck a product against legal and compliance requirements and collect evidence for counsel to review
check_continuityCheck continuity across surfaces (pricing, terminology, promises) between marketing, product, docs, and emails
stuntdouble_guideOrientation for Stunt Double: what it does, when to reach for it, and the full tool catalogue

Workspace member administration (inviting/removing members) is available in the web dashboard.

Transport

This server uses Streamable HTTP transport. The endpoint is:

https://app.stuntdouble.io/api/mcp

Links

Verifying changes

From the repo root:

node scripts/validate-json.mjs
npx --yes prettier@3.4.2 --check README.md mcp.json server.json .cursor-plugin/plugin.json

More context in CONTRIBUTING.md. GitHub Actions runs the same checks on push and pull requests.

License

MIT

Reviews

No reviews yet

Be the first to review this server!