The master skill in PlanetScale's official pack: runs a full read-only best-practices assessment of a database or org, then produces one evidence-backed report.
MCP BuilderSkill
Summary
Anthropic's guide for building high-quality MCP servers end to end — research, tool design, implementation in TypeScript or Python, testing, and a 10-question evaluation suite.
Features
- Four-phase workflow: research, implementation, review and test, evaluation
- Guidance on balancing comprehensive API coverage against workflow tools
- Concrete schema rules using Zod (TypeScript) or Pydantic (Python)
- Covers outputSchema, structuredContent and the four tool annotations
- Prescribes a recommended stack: TypeScript, streamable HTTP, stateless JSON
- Testing via the MCP Inspector for both TypeScript and Python servers
- Generates a 10-question XML evaluation suite you can re-run as regressions
Install This Skill
Add this skill to your favorite AI agent in a few steps.
Skill Content
Usage Instructions
Learn how to use this skill with different AI agents.
Example Usage
Build me an MCP server for the Linear API in TypeScript.
The skill takes over: it reads the MCP spec and the Linear API docs, proposes a tool surface, implements with Zod schemas and structured output, tests through the MCP Inspector, and finishes by writing ten evaluation questions to verify an agent can actually use what it built.
Description
MCP Builder is Anthropic's official skill for writing Model Context Protocol servers, and it is aimed squarely at the gap between "the server runs" and "an agent can actually get work done with it." Its stated measure of quality is not endpoint coverage but how well an LLM accomplishes real-world tasks through the tools you expose.
It walks a four-phase process. Phase 1 is research: read the MCP specification (the skill points at the sitemap and the .md-suffixed pages), read the SDK docs, then read the API you are wrapping and decide which tools to build. It takes a clear position on the perennial design question — balance comprehensive API coverage against specialised workflow tools, and when in doubt prefer coverage, because clients differ in whether they compose primitives via code execution or want higher-level workflows.
Phase 2 is implementation, with concrete rules rather than platitudes: Zod or Pydantic input schemas with constraints and examples in the field descriptions, outputSchema and structuredContent for machine-readable responses, consistent prefixed tool names such as github_create_issue, pagination, and the four behavioural annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). Error messages are treated as an agent-facing interface: they should name a next step, not just a failure.
Phase 3 covers build and manual testing through the MCP Inspector. Phase 4 is the part most server authors skip — writing ten evaluation questions that are independent, read-only, complex enough to need several tool calls, realistic, verifiably single-answer and stable over time, emitted as an XML question/answer file you can re-run as a regression suite.
The skill has an explicit recommended stack: TypeScript for the SDK quality and MCPB compatibility, streamable HTTP with stateless JSON for remote servers, stdio for local ones. Python via FastMCP is fully supported as the alternative, and the skill ships separate reference guides for each language plus an MCP best-practices document.
Part of the anthropics/skills repository (Apache 2.0 for this skill). Useful whether you are wrapping an internal service or publishing a public server, and particularly worth reading before you commit to a tool surface, since that is the decision hardest to change later.
Related Skills
Build crash-safe AI agents on AgentKit and step.ai — durable tool calls, human-in-the-loop approval, realtime progress, and when not to reach for an agent loop at all.
Inngest's durable-execution playbook as an agent skill — steps and memoisation, event and cron triggers, idempotency, cancellation, retries and non-retriable errors.
Temporal's official skill for building durable workflows — SDK patterns across seven languages, plus the determinism rules that decide whether a workflow survives a replay.