mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
91
73%
Does it follow best practices?
Impact
93%
2.21xAverage score across 10 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/anthropic-mcp-builder/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly identifies its niche (MCP server development) and provides explicit 'Use when' guidance with framework-specific triggers. Its main weakness is that it could be more specific about the concrete actions it covers (e.g., defining tools, configuring transports, handling authentication) rather than staying at the high-level 'creating servers' framing.
Suggestions
Add specific concrete actions the skill covers, e.g., 'defining tools and resources, configuring transports, structuring server code, handling authentication' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MCP servers) and a general action ('creating high-quality MCP servers that enable LLMs to interact with external services through well-designed tools'), but doesn't list multiple specific concrete actions like defining tools, handling authentication, setting up transport layers, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (creating high-quality MCP servers that enable LLMs to interact with external services through well-designed tools) and 'when' (explicitly states 'Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK)'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'MCP', 'Model Context Protocol', 'MCP servers', 'FastMCP', 'MCP SDK', 'external APIs', 'Python', 'Node', 'TypeScript', 'tools'. These cover the main variations a user building MCP servers would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | MCP server development is a very specific niche with distinct trigger terms (MCP, Model Context Protocol, FastMCP, MCP SDK). This is unlikely to conflict with general coding skills or other integration-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured guide that effectively organizes a complex multi-phase workflow with good progressive disclosure to reference files. However, it falls short on actionability by deferring most concrete implementation details to reference files (which aren't provided in the bundle) and includes some verbose explanations of concepts Claude already knows. The workflow would benefit from explicit validation checkpoints and feedback loops, particularly around testing and error recovery.
Suggestions
Add at least one minimal but complete inline code example showing a basic MCP tool registration (in TypeScript) so the skill is actionable even without loading reference files.
Add explicit validation feedback loops in Phase 3, e.g., 'If build fails: check type errors → fix → rebuild. If Inspector test fails: verify tool schemas → check error messages → re-test.'
Remove the duplicated Reference Files section at the end, since all those links are already provided inline at the relevant phases—or consolidate all references to only one location to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary explanation (e.g., explaining why TypeScript is recommended with multiple justifications, explaining what MCP is). Some sections like 'Understand Modern MCP Design' contain general advice Claude would already know (DRY principle, async/await for I/O). The reference files section at the end largely duplicates links already provided inline throughout the phases. | 2 / 3 |
Actionability | The skill provides a structured process with some concrete commands (npm run build, npx inspector, python -m py_compile) but lacks executable code examples for the core task of actually building an MCP server. Most guidance is at the level of 'create shared utilities' or 'implement tools' without showing concrete implementation patterns inline—those are deferred to reference files that aren't provided in the bundle. | 2 / 3 |
Workflow Clarity | The four-phase workflow is clearly sequenced and logically ordered, but validation checkpoints are weak. Phase 3 mentions 'run build' and 'test with MCP Inspector' but lacks explicit feedback loops (e.g., what to do if build fails, how to verify tools work correctly before moving to Phase 4). For a multi-step process involving API integration and server development, the absence of explicit validate-fix-retry loops is notable. | 2 / 3 |
Progressive Disclosure | The skill effectively uses a hub-and-spoke model with clear one-level-deep references to language-specific guides, best practices, evaluation guide, and external SDK documentation. References are well-signaled with emoji icons and descriptive summaries of what each linked file contains. The reference files section at the end provides a clear navigation index. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- boisenoise/skills-collections
- Commit
8ac11ab
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.