Borrowing it
Nothing to install: this file belongs to HoziMurayama/Multi-LLM-Debugging-Bridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HoziMurayama/Multi-LLM-Debugging-Bridge/master/.claude/skills/setup-mcp-server/SKILL.mdgit clone --depth 1 https://github.com/HoziMurayama/Multi-LLM-Debugging-BridgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hozimurayama/multi-llm-debugging-bridge/setup-mcp-server)<a href="https://agentmods.dev/skills/hozimurayama/multi-llm-debugging-bridge/setup-mcp-server"><img src="https://agentmods.dev/badge/skills/hozimurayama/multi-llm-debugging-bridge/setup-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hozimurayama/multi-llm-debugging-bridge/setup-mcp-server"><img src="https://agentmods.dev/badge/skills/hozimurayama/multi-llm-debugging-bridge/setup-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01342 |
| Opus 5.5 | $0.00013 | $0.00537 |
| Sonnet 5.5 | $0.00007 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
setup-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to setup-mcp-server — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup mcp-rubber-duck
You are setting up mcp-rubber-duck as an MCP server in an AI coding tool.
Reference
.claude/skills/setup-mcp-server/references/tool-configs.md— per-tool JSON/YAML config templates.claude/skills/setup-mcp-server/references/provider-env-vars.md— env var reference.claude/skills/setup-mcp-server/references/troubleshooting.md— common issues
Supported tools and config paths
| Tool | Config File (macOS) | Key | Notes |
|---|---|---|---|
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json |
mcpServers |
Windows: %APPDATA%\Claude\claude_desktop_config.json |
| Claude Code (user) | ~/.claude.json |
mcpServers |
Prefer claude mcp add CLI |
| Claude Code (project) | .mcp.json |
mcpServers |
Shared via VCS |
| Cursor (project) | .cursor/mcp.json |
mcpServers |
|
| Cursor (global) | ~/.cursor/mcp.json |
mcpServers |
|
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
mcpServers |
Supports ${env:VAR} |
| VS Code | .vscode/mcp.json |
servers |
Different key name! Uses ${env:VAR} |
| Continue | .continue/config.yaml |
mcpServers (array) |
YAML format |
ChatGPT supports MCP via UI only (Developer Mode > Add MCP Server), not a config file.
1. Determine target tool
If $ARGUMENTS specifies a tool name, use it. Otherwise ask the user:
Supported tools: claude-desktop, claude-code, cursor, windsurf, vscode, continue
2. Detect platform
Run uname -s to detect macOS / Linux / Windows (Git Bash). This affects config file paths.
3. Detect install method
Check in order:
which mcp-rubber-duck— if found, usemcp-rubber-duckas the command- If we're inside the mcp-rubber-duck repo (check for
package.jsonwith"name": "mcp-rubber-duck"), offer from-source vianode dist/index.js - Default to
npx -y mcp-rubber-duck
4. Ask about providers
Ask the user which providers to include. Offer these choices:
- OpenAI (
OPENAI_API_KEY) — most popular - Google Gemini (
GEMINI_API_KEY) - Groq (
GROQ_API_KEY) — fast inference - Ollama (local, no key needed)
- CLI agents (Claude CLI, Codex, Gemini CLI, Aider)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 119 lines · 33 tokens per session scan A 28d6e316a48e
setup-mcp-server is a skill published in the GitHub repository HoziMurayama/Multi-LLM-Debugging-Bridge (6 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 1,342 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to setup-mcp-server, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…