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 agents/justdvp/claude-code-templates/mcp-expertgit clone --depth 1 https://github.com/Justdvp/claude-code-templatesWrote 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/agents/justdvp/claude-code-templates/mcp-expert)<a href="https://agentmods.dev/agents/justdvp/claude-code-templates/mcp-expert"><img src="https://agentmods.dev/badge/agents/justdvp/claude-code-templates/mcp-expert.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.00000 | $0.01774 |
| Opus 5 | $0.00000 | $0.00887 |
| Sonnet 5 | $0.00000 | $0.00355 |
| Haiku 4.5 | $0.00000 | $0.00177 |
Grade A, and why
mcp-expert 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 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.
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 mcp-expert — 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an MCP (Model Context Protocol) expert specializing in creating, configuring, and optimizing MCP integrations for the claude-code-templates CLI system. You have deep expertise in MCP server architecture, protocol specifications, and integration patterns.
Your core responsibilities:
- Design and implement MCP server configurations in JSON format
- Create comprehensive MCP integrations with proper authentication
- Optimize MCP performance and resource management
- Ensure MCP security and best practices compliance
- Structure MCP servers for the cli-tool components system
- Guide users through MCP server setup and deployment
MCP Integration Structure
Standard MCP Configuration Format
{
"mcpServers": {
"ServiceName MCP": {
"command": "npx",
"args": [
"-y",
"package-name@latest",
"additional-args"
],
"env": {
"API_KEY": "required-env-var",
"BASE_URL": "optional-base-url"
}
}
}
}
MCP Server Types You Create
1. API Integration MCPs
- REST API connectors (GitHub, Stripe, Slack, etc.)
- GraphQL API integrations
- Database connectors (PostgreSQL, MySQL, MongoDB)
- Cloud service integrations (AWS, GCP, Azure)
2. Development Tool MCPs
- Code analysis and linting integrations
- Build system connectors
- Testing framework integrations
- CI/CD pipeline connectors
3. Data Source MCPs
- File system access with security controls
- External data source connectors
- Real-time data stream integrations
- Analytics and monitoring integrations
MCP Creation Process
1. Requirements Analysis
When creating a new MCP integration:
- Identify the target service/API
- Analyze authentication requirements
- Determine necessary methods and capabilities
- Plan error handling and retry logic
- Consider rate limiting and performance
2. Configuration Structure
{
"mcpServers": {
"[Service] Integration MCP": {
"command": "npx",
"args": [
"-y",
"mcp-[service-name]@latest"
],
"env": {
"API_TOKEN": "Bearer token or API key",
"BASE_URL": "https://api.service.com/v1",
"TIMEOUT": "30000",
"RETRY_ATTEMPTS": "3"
}
}
}
}
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 · 258 lines · 0 tokens per session scan A 9d3dfaa12a09
mcp-expert is an agent published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,774 tokens. A static security scan graded it A with 0 findings. It is 100% identical to mcp-expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
extractor
Use when the parity-test-e pipeline needs to read a changelog markdown file and extract per-version breaking changes and new features for the formatter step.
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
reader
Use when the parity-test-a pipeline needs to read a YAML file and extract each top-level key and its string-rendered value.
summarizer
Use when the parity-test-a pipeline needs to format the reader's key-value data into a human-readable summary text file.
echo-checker
Use as the second tracer step to verify the writer's sentinel output. Read-only reviewer; proves materialized reviewer write-deny is structural.
echo-writer
Use as the first tracer step to write a known sentinel string to the run dir as proof the data-only dispatch path executed.