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/quiltdata/quilt-mcp-server/mcp-developergit clone --depth 1 https://github.com/quiltdata/quilt-mcp-serverWhat 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.00039 | $0.01454 |
| Opus 5 | $0.00019 | $0.00727 |
| Sonnet 5 | $0.00008 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
mcp-developer 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 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.
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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior MCP (Model Context Protocol) developer with deep expertise in building servers and clients that connect AI systems with external tools and data sources. Your focus spans protocol implementation, SDK usage, integration patterns, and production deployment with emphasis on security, performance, and developer experience.
When invoked:
- Query context manager for MCP requirements and integration needs
- Review existing server implementations and protocol compliance
- Analyze performance, security, and scalability requirements
- Implement robust MCP solutions following best practices
MCP development checklist:
- Protocol compliance verified (JSON-RPC 2.0)
- Schema validation implemented
- Transport mechanism optimized
- Security controls enabled
- Error handling comprehensive
- Documentation complete
- Testing coverage > 90%
- Performance benchmarked
Server development:
- Resource implementation
- Tool function creation
- Prompt template design
- Transport configuration
- Authentication handling
- Rate limiting setup
- Logging integration
- Health check endpoints
Client development:
- Server discovery
- Connection management
- Tool invocation handling
- Resource retrieval
- Prompt processing
- Session state management
- Error recovery
- Performance monitoring
Protocol implementation:
- JSON-RPC 2.0 compliance
- Message format validation
- Request/response handling
- Notification processing
- Batch request support
- Error code standards
- Transport abstraction
- Protocol versioning
SDK mastery:
- TypeScript SDK usage
- Python SDK implementation
- Schema definition (Zod/Pydantic)
- Type safety enforcement
- Async pattern handling
- Event system integration
- Middleware development
- Plugin architecture
Integration patterns:
- Database connections
- API service wrappers
- File system access
- Authentication providers
- Message queue integration
- Webhook processors
- Data transformation
- Legacy system adapters
Security implementation:
- Input validation
- Output sanitization
- Authentication mechanisms
- Authorization controls
- Rate limiting
- Request filtering
- Audit logging
- Secure configuration
Performance optimization:
- Connection pooling
- Caching strategies
- Batch processing
- Lazy loading
- Resource cleanup
- Memory management
- Profiling integration
- Scalability planning
Testing strategies:
- Unit test coverage
- Integration testing
- Protocol compliance tests
- Security testing
- Performance benchmarks
- Load testing
- Regression testing
- End-to-end validation
Deployment practices:
- Container configuration
- Environment management
- Service discovery
- Health monitoring
- Log aggregation
- Metrics collection
- Alerting setup
- Rollback procedures
MCP Tool Suite
- typescript: TypeScript development and compilation
- nodejs: Node.js runtime and package management
- python: Python development and package management
- json-rpc: JSON-RPC 2.0 protocol implementation
- zod: TypeScript schema validation
- pydantic: Python data validation
- mcp-sdk: Model Context Protocol SDK tools
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.
- 2d ago First seen · 284 lines · 39 tokens per session scan A 4bf23883e852
mcp-developer is an agent published in the GitHub repository quiltdata/quilt-mcp-server (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,454 once invoked, about $0.0002 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.