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 instructions/itstanner5216/multi-mcp/claude-mdgit clone --depth 1 https://github.com/itstanner5216/multi-mcpWrote 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/instructions/itstanner5216/multi-mcp/claude-md)<a href="https://agentmods.dev/instructions/itstanner5216/multi-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/itstanner5216/multi-mcp/claude-md.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.03073 | $0.03073 |
| Opus 5 | $0.01537 | $0.01537 |
| Sonnet 5 | $0.00615 | $0.00615 |
| Haiku 4.5 | $0.00307 | $0.00307 |
Grade A, and why
multi-mcp CLAUDE.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Multi-MCP is a Python-based proxy server that acts as a single MCP (Model Context Protocol) server while connecting to and routing between multiple backend MCP servers. It supports both STDIO and SSE (Server-Sent Events) transports and can dynamically add/remove MCP servers at runtime.
Architecture
Core Components
- MultiMCP (
src/multimcp/multi_mcp.py): Main server orchestrator that handles configuration, transport modes, and HTTP endpoints - MCPProxyServer (
src/multimcp/mcp_proxy.py): Core proxy that forwards MCP requests to backend servers, handles tool namespacing (server_name_tool_name), and manages capabilities aggregation - MCPClientManager (
src/multimcp/mcp_client.py): Manages lifecycle of multiple MCP client connections (both stdio and SSE) - Logger (
src/utils/logger.py): Centralized logging using loguru withmulti_mcp.*namespace
Key Patterns
- Tool Namespacing: Tools are namespaced as
server_name__tool_name(double underscore separator) to avoid conflicts when multiple servers expose tools with the same name - Transport Flexibility: Supports both STDIO (for CLI/pipe-based) and SSE (for HTTP/network-based) communication
- Dynamic Server Management: Can add/remove MCP servers at runtime via HTTP API (SSE mode only)
- Capability Aggregation: Proxies and combines tools, prompts, and resources from all connected backend servers
Development Commands
Running the Server
# STDIO mode (default)
uv run main.py --transport stdio
# SSE mode with custom host/port
uv run main.py --transport sse --host 0.0.0.0 --port 8080
# With custom config file
uv run main.py --config ./examples/config/mcp_k8s.json
# Quick development run
make run
Testing
# Individual test suites
make test-proxy # Core proxy functionality
make test-e2e # End-to-end integration tests
make test-lifecycle # Client lifecycle management
make test-k8s # Kubernetes deployment tests (requires docker-build)
# All tests
make all-test
# Run specific test file directly
pytest -s tests/proxy_test.py
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.
- 3d ago First seen · 304 lines · 3,073 tokens per session scan A 17d48792f1a6
multi-mcp CLAUDE.md is an instructions file published in the GitHub repository itstanner5216/multi-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 3,073 tokens to every session, about $0.0154 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.