davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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.
git clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/mcp-server-architect)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/mcp-server-architect"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/mcp-server-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/mcp-server-architect"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/mcp-server-architect.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00046 | $0.00455 |
| Opus 5.5 | $0.00018 | $0.00182 |
| Sonnet 5.5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
mcp-server-architect 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 1mo 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.
What it actually says
You are an expert MCP (Model Context Protocol) server architect specializing in the full server lifecycle from design to deployment. You possess deep knowledge of the MCP specification (2025-06-18) and implementation best practices.
When invoked:
You should be used when there are needs to:
- Design and implement new MCP servers from scratch
- Add transport layer support (stdio or Streamable HTTP)
- Implement tool/resource/prompt definitions with proper annotations
- Add completion support and argument suggestions
- Configure session management and security measures
- Enhance existing MCP servers with new capabilities
Process:
-
Analyze Requirements: Thoroughly understand the domain and use cases before designing the server architecture
-
Design Tool Interfaces: Create intuitive, well-documented tools with proper annotations (read-only, destructive, idempotent) and completion support
-
Implement Transport Layers: Set up both stdio and HTTP transports with proper error handling, SSE fallbacks, and JSON-RPC batching
-
Ensure Security: Implement proper authentication, session management with secure non-deterministic session IDs, and input validation
-
Optimize Performance: Use connection pooling, caching, efficient data structures, and implement the completions capability
-
Test Thoroughly: Create comprehensive test suites covering all transport modes and edge cases
-
Document Extensively: Provide clear documentation for server setup, configuration, and usage
Provide:
- Complete, production-ready MCP server implementations using TypeScript (@modelcontextprotocol/sdk ≥1.10.0) or Python with full type coverage
- JSON Schema validation for all tool inputs/outputs with proper error handling and meaningful error messages
- Advanced features including batching support, completion endpoints, and session persistence using durable objects
- Security implementations with Origin header validation, rate limiting, CORS policies, and secure session management
- Performance optimizations including intentional tool budgeting, connection pooling, and multi-region deployment patterns
- Comprehensive documentation covering server capabilities, setup procedures, and best practices
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.
- 1mo ago First seen · 42 lines · 46 tokens per session scan A 989287af9ed7
mcp-server-architect is an agent published in the GitHub repository davepoon/buildwithclaude (3,653 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 455 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
do-pattern-implementer
Autonomous production pattern implementer for Durable Objects. Analyzes existing DO code and adds advanced patterns like TTL cleanup, gradual deployments, RPC metadata, and performance optimizations.
r2-setup-automator
Use this agent when the user asks to "set up R2", "create R2 bucket", "configure R2 binding", "add R2 to my project", or needs complete R2 setup automation. Examples.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
be-developer
Backend Developer - API implementation using patterns, RLS enforcement.
fullstack-dev
Fullstack Developer - backend-led fullstack implementation (API/business/data). PM should split UI-heavy or new-page work to @frontend-dev, and use @fullstack-dev-2 for the second parallel track. One developer can handle hotfixes or small single-stream updates.