agentmods.dev

mcp

A project command for managing MCP (Model Context Protocol) servers, which let an agent use tools supplied by external services.

In plain words
What is it for?
Use it to list configured servers, inspect their status, add servers from the Smithery Registry, and configure their project permissions.
Why use it?
It keeps server configuration and permissions in one place and shows how each server's tools can be called. It also helps check whether a server is configured correctly.

Command for Claude Code

11 4mo ago B scan 18 tokens original MIT
View the source file brain-bootstrap/claude-code-brain-bootstrap
Install

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.

agentmods
npx agentmods add commands/brain-bootstrap/claude-code-brain-bootstrap/mcp
Clone the repo
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 919 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00919
Opus 5 $0.00009 $0.00460
Sonnet 5 $0.00004 $0.00184
Haiku 4.5 $0.00002 $0.00092

Measured 2d ago against content hash 2603bf5ac257, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

mcp 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 2d 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 MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

- **NEVER** hardcode API keys in `.mcp.json` — use env var placeholders like `"YOUR_API_KEY_HERE"`
.claude/commands/mcp.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Model Context Protocol (MCP) servers for this project: $ARGUMENTS

ultrathink — use extended reasoning for MCP server selection and configuration.

MCP Tool Invocation Format

Once servers are configured in .mcp.json, invoke their tools using:

mcp__SERVER_KEY__TOOL_FUNCTION_NAME

Where SERVER_KEY is the key in .mcp.json under mcpServers.

Instructions

If $ARGUMENTS contains list or is empty:

  1. Read .mcp.json to show currently configured servers
  2. Show the invocation format for each tool
  3. Suggest additional servers based on the tech stack in claude/architecture.md

If $ARGUMENTS contains add <server-name>:

  1. Check if the server name exists in the Smithery Registry: https://registry.smithery.ai/servers/<name>
  2. Add the server configuration to .mcp.json under mcpServers
  3. Update .claude/settings.json to include allowedTools permissions for the new server
  4. Update CLAUDE.md — add a note to the Plugin Ecosystem or Critical Patterns section

If $ARGUMENTS contains status:

  1. Read .mcp.json — list all configured servers with their connection type
  2. Check which tools each server provides
  3. Verify allowedTools in .claude/settings.json is in sync with .mcp.json

If $ARGUMENTS contains format or invocations:

Show all available MCP tool invocations from the current .mcp.json:

mcp__SERVER_KEY__TOOL_NAME

Common MCP Servers by Project Type

Web / Frontend projects

  • github — mcp__github__create_pull_request, mcp__github__list_commits
  • web-search — mcp__web-search__search (documentation lookup)
  • filesystem — mcp__filesystem__read_file, mcp__filesystem__write_file

Backend / API projects

  • postgres — mcp__postgres__query (read-only DB access)
  • github — PR management, issue tracking
  • web-search — API documentation, best practices

Data Science / ML projects

  • filesystem — data file access
  • web-search — research papers, library docs
  • documents — reading large datasets or PDFs

Read the full file on GitHub · 108 lines

Changes

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.

  1. 2d ago First seen · 108 lines · 18 tokens per session scan B 2603bf5ac257

Subscribe to this mod's changes

mcp is a command published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 919 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AIclaude-codeclaude-configclaude-context
Related

Other commands, from other repositories

restart

Restart the claude-mnemonic worker process. Use this command when experiencing issues with the memory system.

lukaszraczylo/claude-mnemonic · 0 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens