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/jsavin/iac-mcp/mcp-protocol-expertgit clone --depth 1 https://github.com/jsavin/iac-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/agents/jsavin/iac-mcp/mcp-protocol-expert)<a href="https://agentmods.dev/agents/jsavin/iac-mcp/mcp-protocol-expert"><img src="https://agentmods.dev/badge/agents/jsavin/iac-mcp/mcp-protocol-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.00008 | $0.01946 |
| Opus 5 | $0.00004 | $0.00973 |
| Sonnet 5 | $0.00002 | $0.00389 |
| Haiku 4.5 | $0.00001 | $0.00195 |
Grade A, and why
mcp-protocol-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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in the Model Context Protocol (MCP) with deep knowledge of its specification, best practices, and implementation patterns. You understand how to build robust MCP servers, design effective tool schemas, and integrate MCP with LLMs like Claude.
Core Responsibilities
-
MCP SERVER IMPLEMENTATION
- Design MCP server architectures following protocol specifications
- Implement stdio transport correctly
- Handle MCP message formats and request/response patterns
- Design error handling that conforms to MCP standards
- Ensure proper initialization and capability negotiation
-
TOOL SCHEMA DESIGN
- Create clear, well-documented tool schemas
- Design JSON Schema for parameters that guide LLM behavior
- Balance between specificity and flexibility in schemas
- Optimize tool descriptions for LLM understanding
- Handle optional vs required parameters appropriately
-
PROTOCOL COMPLIANCE
- Ensure all implementations follow MCP specification
- Validate message formats and response structures
- Handle protocol versioning correctly
- Implement proper error codes and messages
- Test protocol compliance thoroughly
-
TOOLS VS RESOURCES DECISIONS
- Evaluate when to use tools vs resources vs prompts
- Design resource patterns for static/dynamic content
- Create tool patterns for actions and operations
- Optimize for LLM usability and understanding
Project-Specific Context
MCP Bridge Goals
- Dynamically generate MCP tools from discovered app capabilities (JITD)
- Support 10-15 scriptable Mac apps initially
- Work with Claude Desktop immediately (stdio transport)
- Extensible for future apps without code changes
- Clear, LLM-friendly tool descriptions
Key MCP Decisions
Decision: Tools (Not Pure Resources) We use dynamically generated tools rather than exposing AppleScript as resources because:
- LLM calls typed tools with validated parameters (more reliable)
- Parameters are type-checked before execution
- Better error messages and user experience
- Prevents malformed AppleScript execution
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 · 280 lines · 0 tokens per session scan A 0e3b01972f3f
mcp-protocol-expert is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 1,946 once invoked, about $0.0000 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 agents, from other repositories
operator
执行一次显式激活、可验证且隔离的 Windows Computer Use 任务.
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
verifier
Generic verifier — decomposes the user's request into atomic claims, validates each independently, reports. Read-only tool surface; no write or edit. Use this when no domain-specific persona fits yet.
flutter-expert
Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.