Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Tells you how you and your Claude agent actually work together. Local-only, no API keys.
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"dearuser": {
"command": "npx",
"args": [
"-y",
"@poisedhq/dearuser-mcp"
]
}
}
}Run this in your terminal
claude mcp add dearuser -- npx -y @poisedhq/dearuser-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"dearuser": {
"command": "npx",
"args": [
"-y",
"@poisedhq/dearuser-mcp"
]
}
}
}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": {
"dearuser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@poisedhq/dearuser-mcp"
]
}
}
}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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account bleedmode, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.20) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Binggio
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.
Governed answers from your data: approved meanings only, refusals instead of guesses.
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.
Your AI agent works for you — but how well do you work together?
Dear User is an open-source tool that audits your Claude Code setup and tells you exactly what to fix. It scores your collaboration, finds leaked secrets and config conflicts, and checks system health — all locally, nothing uploaded unless you explicitly share your Wrapped card.
claude mcp add --scope user dearuser -- npx -y @poisedhq/dearuser-mcp@latest
Then ask Claude: *"Analyze my collaboration with Claude"*
Landing: dearuser.ai · Feedback: use the feedback tool in Claude, or open an issue
Dear User is an MCP server (Model Context Protocol — the plugin system Claude Code and Claude Desktop use). Once installed, it shows up as a set of tools your agent can call. No GUI, no sign-up, no cloud account.
Three local reports, one shareable Wrapped card, one feedback channel:
| Tool | What it does | Example prompt |
|---|---|---|
collab | Full collaboration report — persona, 0-100 score, friction patterns, specific recommendations | *"How good is my Claude setup?"* |
security | Leaked secrets, prompt-injection surfaces, rule conflicts in your agent contract (CLAUDE.md or AGENTS.md) | *"Check my config for leaked API keys"* |
health | Structural coherence — orphan scheduled tasks, overlapping skills, dead hooks | *"Is anything broken in my setup?"* |
wrapped | Spotify-style shareable stats card — scores + counts + persona. Opt-in public URL via share_report. | *"Give me my Dear User Wrapped"* |
feedback | Send a note to the Dear User inbox | *"Send feedback: the health report could be shorter"* |
Plus helpers: onboard (7-step guided setup), history (trend without re-scanning), help (menu), implement_recommendation, dismiss_recommendation, share_report (Wrapped-only upload).
wrapped, then share_report to get a dearuser.ai/r/ URL for your stats card. Anonymized before upload (paths collapsed to basenames, emails stripped, secrets redacted). Collab/security/health reports stay local — findings can carry business context that isn't safe to auto-share.research/calibration/ for both studies.One command per client. Full guide: docs/install.md.
Claude Code (CLI)
claude mcp add --scope user dearuser -- npx -y @poisedhq/dearuser-mcp@latest
Restart Claude Code afterwards so the tools appear.
Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "dearuser": { "command": "npx", "args": ["@poisedhq/dearuser-mcp"] } } }
Cursor, Windsurf, Cline, Zed — see docs/install.md.
Optional: install the slash commands (see Commands for the full list) so you can type /dearuser-collab instead of asking in prose:
npx -p @poisedhq/dearuser-mcp dearuser-install-skills
After installing, restart your client and try these in order:
Run Dear User collab on this project
You'll get a persona (Vibe Coder / Senior Developer / Indie Hacker / Venture Studio / Team Lead), a 0-100 score across 7 categories, and 3-10 concrete recommendations.
Run Dear User security
Checks your agent contract (CLAUDE.md or AGENTS.md), memory, skills and hooks for leaked tokens, injection surfaces and rule conflicts.
Share my collab report
Returns a dearuser.ai/r/ link. Anonymized before upload. You choose whether to paste it anywhere.
Example output from collab:
Persona: Indie Hacker (87% confidence)
Score: 73 / 100
Top friction: • Quality Standards — no test-before-commit rule in CLAUDE.md • Memory Health — 2 memory files haven't been touched in 90+ days • Communication — no language preference stated (English vs Danish mixing)
Recommendations (3 shown, 5 total):
Eight slash commands ship with Dear User. Ask your agent by name, or type the slash command if you installed them with dearuser-install-skills.
| Command | What it does |
|---|---|
/dearuser-collab | Collaboration analysis — persona, 0-100 score across 7 categories, prioritized recommendations. |
/dearuser-health | System health — orphan jobs, overlap, stale schedules, missing MCP registrations, reconciliation gaps. |
/dearuser-security | Secret scan, prompt-injection surfaces, and rule conflicts in your agent contract. |
/dearuser-wrapped | Shareable collaboration stats in a Spotify-Wrapped style card. |
/dearuser-onboard | Conversational 7-step setup for first-time users. |
/dearuser-history | Show your last reports, score trend over time, or what changed since the last run — no re-scan. |
/dearuser-feedback | Send a short note (bug, request, reaction) to the Dear User founders. |
/dearuser-help | Show what Dear User can do and list every tool. |
Three in-chat actions the agent can call for you: share_report (upload a Wrapped card to dearuser.ai/r/ ), implement_recommendation (apply a pending recommendation), dismiss_recommendation (mark one irrelevant).
Dear User is local-first. Your scans stay on your machine:
~/.dearuser/dearuser.db (SQLite, WAL mode)The only exceptions are things you explicitly trigger:
dearuser.ai so you can share a URL. Your local DB is not modified. You can set an expires_at to auto-expire the link. Collab/security/health reports are NOT shareable — findings can carry business context (project names, client names, architecture notes) we don't think should live on a public URL.No other tool transmits anything. If share_report isn't configured with DEARUSER_SUPABASE_URL + DEARUSER_SUPABASE_SERVICE_KEY, it errors out cleanly and the rest of Dear User keeps working.
Full privacy details: docs/privacy.md.
Your files (CLAUDE.md or AGENTS.md, memory, hooks, skills, sessions)
│ Scanner ──► Parser ──► Engines (scoring, secrets, conflicts, health) │ Persona detection → Scoring → Gap analysis → Recommendations │ Feedback loop (tracks which recommendations you implemented) │ ~/.dearuser/dearuser.db ← dashboard reads from here
mcp/ — @poisedhq/dearuser-mcp npm package (the MCP server). See mcp/README.md for development notes.web/ — dearuser.ai landing + share-report pages (Astro).docs/ — install guide, privacy doc, per-platform setup (Supabase/GitHub/Vercel for the optional security platform advisors).research/ — calibration data + architecture notes we're willing to share.See CONTRIBUTING.md. Bug reports and small fixes welcome via GitHub issues and PRs.
feedback MCP tool from inside ClaudeDear User is MIT-licensed. See LICENSE.
Open-core commitment: everything in this repo is MIT and stays MIT. If we ever build team or hosted features (agency dashboards, cross-project trend lines, vertical-specific benchmarks), they'll live in separate repos with their own license — never by pulling pieces out of this one.