MCP server development guide — agent-centric tool design
Build high-quality MCP servers in Python (FastMCP) or TypeScript — agent-centric design principles, implementation phases, review checklist and evaluation harness
- What
- Build high-quality MCP servers in Python (FastMCP) or TypeScript — agent-centric design principles, implementation phases, review checklist and evaluation harness
- Cost
- Free
- Needs
- a service API to integrate and an MCP-capable setup (Python or Node/TypeScript toolchains) — the skill is a development guide the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license — its terms live in a LICENSE.txt the manifest could not confirm, so no content is reproduced): @composiohq's mcp-builder skill — the guide for creating high-quality MCP servers in Python (FastMCP) or Node/TypeScript (MCP SDK). Phase 1: deep research and planning — agent-centric design principles (build for workflows not API endpoints, optimize for limited context, actionable error messages, natural task subdivisions, evaluation-driven development), study the MCP protocol and SDK docs, exhaustively study the target API's docs, then write an implementation plan (tool selection, shared utilities, input/output design, error-handling strategy). Phase 2: implementation — project setup, core infrastructure first, systematic tool implementation (Pydantic/Zod input schemas, comprehensive docstrings, tool annotations like readOnlyHint/idempotentHint), language-specific best practices. Phase 3: review and refine — DRY/composability/consistency/type-safety review, safe testing (never run the server in the main process), quality checklists. Phase 4: evaluations — 10 complex, realistic, read-only, verifiable evaluation questions in a prescribed XML format. Honest caveats: guidance only — the agent must already run Claude Code and needs a service API to integrate; similar concept to the existing `anthropics-mcp-builder` listing (different author, different content — not a duplicate); license terms live in the repo's LICENSE.txt, unverified here — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a service API to integrate and an MCP-capable setup (Python or Node/TypeScript toolchains) — the skill is a development guide the agent follows, not software Install "MCP server development guide — agent-centric tool design" for me. It gives my agent @composiohq's 4-phase MCP server workflow: deep research and planning (agent-centric design principles, protocol and SDK study, exhaustive API study, implementation plan), implementation (shared utilities first, systematic tool implementation with Pydantic/Zod schemas and tool annotations, language best practices), review and refine (quality review, safe testing, checklists), and evaluations (10 complex read-only verifiable questions in XML). Related to but distinct from the existing anthropics-mcp-builder listing. IMPORTANT: the license terms live in the repo's LICENSE.txt (unverified) — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/composiohq/awesome-claude-skills/blob/main/mcp-builder/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mcp-builder". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent which service API to wrap as an MCP server; nothing else — it's a guide). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.