Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http usertapes https://usertapes.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"usertapes": {
"url": "https://usertapes.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"usertapes": {
"type": "http",
"url": "https://usertapes.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account mcdca, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
UserTapes is a session replay tool. This is its Model Context Protocol server: a hosted, stateless JSON-RPC endpoint that lets any MCP client — Claude Code, Claude Desktop, Cursor, or your own agent — query what real users did on your site.
This repo does not contain the server's application source (that lives in the main UserTapes codebase). It exists to document and register the public connection details: the endpoint, its tools, and how to authenticate.
Your coding agent can read your repository, your git history, and your test output. None of that describes what a real person actually did when something broke. UserTapes derives a text transcript from every recorded session — clicks, navigation, errors, rage clicks — so an agent can query sessions the same way it queries anything else, instead of you exporting a video and pasting it into a prompt.
The server is one HTTP endpoint speaking stateless JSON-RPC 2.0 over Streamable HTTP (protocol revision 2025-06-18). Get a token from your account's Agent access page, then add:
{
"mcpServers": { "usertapes": { "url": "https://usertapes.com/mcp", "headers": { "Authorization": "Bearer YOUR_MCP_TOKEN" } } } }
No package install, no local process — the client talks to https://usertapes.com/mcp directly.
| Tool | What it does |
|---|---|
list_sites | The account's sites |
list_tapes | Sessions for a site, newest first, filterable by errors, rage clicks, URL substring, duration, and date range |
read_transcript | One session as a markdown transcript |
get_stats | Aggregate counts over N days |
site_digest | One-call briefing of the last N days |
list_alerts / create_alert / delete_alert | Saved standing watches over sessions (e.g. "notify when a session hits an error on /checkout") |
The MCP token is a distinct, revocable, read-scoped credential — separate from a site's ingest-only tracking token. Its only write surface is alerts; it cannot delete a recording, change a site, or touch billing.
MIT — see LICENSE. (This repo is documentation and a registry manifest; the UserTapes application itself is closed source.)