Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/codealive-ai/ai-driven-development/mcp-managementnpx skills add CodeAlive-AI/ai-driven-development --skill mcp-managementgit clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-developmentWrote 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/codealive-ai/ai-driven-development/mcp-management)<a href="https://agentmods.dev/skills/codealive-ai/ai-driven-development/mcp-management"><img src="https://agentmods.dev/badge/skills/codealive-ai/ai-driven-development/mcp-management.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.02379 |
| Opus 5 | $0.00033 | $0.01189 |
| Sonnet 5 | $0.00013 | $0.00476 |
| Haiku 4.5 | $0.00007 | $0.00238 |
Grade B, and why
mcp-management scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
setup. The project must be trusted in `~/.codex/config.toml` under How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Management
IMPORTANT: After adding, removing, or updating MCP servers, inform the user to restart the affected agent for changes to take effect.
CRITICAL: Before removing any server, use AskUserQuestion to confirm with the user.
Quick Reference (Claude Code)
# Install
claude mcp add --transport http <name> <url>
claude mcp add --transport stdio <name> -- <command> [args...]
claude mcp add-json <name> '<json>' # Full JSON config in one shot
# List/inspect
claude mcp list
claude mcp get <name>
# Remove (confirm with user first!)
claude mcp remove <name>
# OAuth login/logout (for OAuth-protected HTTP servers)
claude mcp login <name>
claude mcp logout <name>
Options must come BEFORE the server name. As of 2026-04, --transport http (Streamable HTTP) is recommended; sse is end-of-life.
Plugin MCP servers connect automatically at session start. Use /reload-plugins to re-init after enabling/disabling a plugin mid-session.
Multi-Agent Installation (npx add-mcp)
Install MCP servers to multiple coding agents at once using add-mcp:
# Remote server (HTTP)
npx add-mcp https://mcp.example.com/mcp
# npm package (stdio)
npx add-mcp @modelcontextprotocol/server-postgres
# Local command
npx add-mcp "npx -y @org/mcp-server --flag value"
# SSE transport
npx add-mcp https://mcp.example.com/sse --transport sse
Options
| Flag | Description |
|---|---|
-g, --global |
Install globally instead of project-level |
-a, --agent <agent> |
Target specific agent(s), repeatable |
-n, --name <name> |
Custom server name |
-t, --transport <type> |
HTTP (default) or SSE |
--header <header> |
Custom HTTP headers, repeatable |
-y, --yes |
Skip confirmation prompts |
--all |
Install to all detected agents |
Supported Agents
| Agent | CLI Argument | Supports Project-Level |
|---|---|---|
| Claude Code | claude-code |
Yes (.mcp.json) |
| Claude Desktop | claude-desktop |
No (global only) |
| Cursor | cursor |
Yes (.cursor/mcp.json) |
| VS Code | vscode |
Yes (.vscode/mcp.json) |
| Gemini CLI | gemini-cli |
Yes (.gemini/settings.json) |
| Codex | codex |
Yes (.codex/config.toml, trusted projects only) |
| Goose | goose |
No (global only) |
| GitHub Copilot CLI | github-copilot-cli |
Yes (.vscode/mcp.json) |
| OpenCode | opencode |
Yes (opencode.json) |
| Zed | zed |
Yes (.zed/settings.json) |
What ships with it
6 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.
- 4d ago First seen · 238 lines · 66 tokens per session scan B 649dc39c4a4d
mcp-management is a skill published in the GitHub repository CodeAlive-AI/ai-driven-development (131 stars, last pushed 5d ago), licensed MIT. It adds 66 tokens to every session and 2,379 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-task
Execute a single subtask from an existing MAP plan via Actor and Monitor. Use when map-plan has decomposed work and you want fine-grained control over one subtask. Do NOT use without an existing plan; run map-plan first.
map-wayfind
Decision-frontier wayfinding: build and work a durable map of open design decisions BEFORE planning, for large or foggy efforts where /map-plan would force premature decomposition. Use when a task is too big or too vague to decompose — many unknowns, tangled decisions, or "I'm not even sure what to build yet" — and…
axum-idioms
Axum HTTP framework patterns — routing, extractors, middleware, state management. For Rust see rust-idioms.
nextjs-idioms
Next.js App Router, RSC, Server Actions, ISR. For React see react-idioms. For TypeScript see typescript-idioms.
hono-idioms
Hono HTTP framework patterns — routing, middleware, Zod validation, RPC client. For TypeScript see typescript-idioms.