CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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).

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/mcp-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly actionable guide with a clear four-phase workflow, concrete build/test commands, and a genuinely useful MCP-specific design section (coverage vs. workflow tools, doc-fetching strategy, tool annotations). Its weaknesses are moderate verbosity — generic software-engineering bullets and a reference library duplicated between Phase 1 and the closing section — and a progressive-disclosure mismatch: every reference points to ./reference/*.md files absent from the actual bundle, while the real bundle's scripts/ evaluation harness is never directly referenced.

Suggestions

Consolidate the duplicated reference material: the SDK URLs and reference-file listings in Phase 1.3 reappear nearly verbatim in the closing 'Reference Files' section — keep one canonical library section (ideally the annotated one) and drop the other.

Cut generic guidance Claude already knows (DRY, 'async/await for I/O operations', 'full type coverage', 'clear tool descriptions' as free-standing bullets) and keep only MCP-specific directives to tighten the token budget.

Fix reference navigation against the real bundle: the four ./reference/*.md links resolve to no files in the bundle, and the existing scripts/ assets (evaluation.py, connections.py, example_evaluation.xml, requirements.txt) are never linked from the body — align paths to the actual layout and reference the evaluation harness scripts directly.

DimensionReasoningScore

Conciseness

Mostly efficient but with unnecessary material that could be tightened: generic bullets Claude already knows ('No duplicated code (DRY principle)', 'Async/await for I/O operations', 'Full type coverage'), and real duplication — the SDK URLs and reference-file listings appear both in Phase 1 ('Use WebFetch to load https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md') and again in the closing 'Reference Files' section, which restates the same four references and what they contain. This fits the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; not 4 because the duplicated reference library and generic quality bullets are more than minor over-explanation, not 2 because the core MCP-specific guidance (coverage-vs-workflow tradeoffs, sitemap-based doc fetching, annotation hints) earns its place.

3 / 5

Actionability

Concrete, executable guidance throughout: exact commands ('npm run build', 'npx @modelcontextprotocol/inspector', 'python -m py_compile your_server.py'), specific fetch instructions ('fetch specific pages with .md suffix', sitemap URL), and a complete, copy-pasteable XML evaluation example with a filled-in qa_pair. This matches 'mostly executable guidance; concrete code or commands with minor gaps'; not 5 because the central tool-implementation section is bullet guidance ('Create shared utilities: API client with authentication') with no code shown inline and relies on the external language guides, and not 3 because the commands and examples given are genuinely executable, not pseudocode.

4 / 5

Workflow Clarity

A clear four-phase sequence (Deep Research and Planning → Implementation → Review and Test → Create Evaluations) with numbered sub-steps and validation checkpoints in Phase 3: 'Run npm run build to verify compilation', 'Test with MCP Inspector', plus a code-quality review checklist, and Phase 4 evaluations acting as an end-to-end feedback loop. This matches 'clear sequence with most checkpoints present; minor validation gaps'; not 5 because no explicit error-recovery loop is spelled out (nothing like 'if build fails, fix and re-run') and the destructive/batch cap does not apply since server building is neither destructive nor batch.

4 / 5

Progressive Disclosure

The body's structure is well designed — one-level-deep references, each clearly signaled with load timing ('Load During Phase 1/2', 'Load During Phase 4') and a summary of contents — but scoring against the actual bundle: all four linked targets ('./reference/mcp_best_practices.md', './reference/node_mcp_server.md', './reference/python_mcp_server.md', './reference/evaluation.md') do not exist in the provided bundle (only a scripts/ directory with connections.py, evaluation.py, example_evaluation.xml, requirements.txt), and the scripts/ files are never directly navigated from the body. References are clearly signaled but the navigation does not resolve against the real bundle structure, so it fits 'some structure but could be better organized'; not 4 because broken paths for every reference plus an unnavigated scripts/ directory is more than a minor organization gap, and not 2 because the in-body organization and signaling itself is strong with no monolithic inlining.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit and concrete 'Use when...' trigger clause, good natural keyword coverage including framework names (FastMCP, TypeScript SDK), and a distinct MCP-server niche with low conflict risk. The only weakness is mild evaluative padding ('high-quality', 'well-designed') in place of additional concrete capability statements.

DimensionReasoningScore

Specificity

Quotes: 'creating high-quality MCP (Model Context Protocol) servers', 'enable LLMs to interact with external services through well-designed tools', 'integrate external APIs or services', with concrete language qualifiers 'Python (FastMCP)' and 'Node/TypeScript (MCP SDK)'. This lists several specific actions (create servers, integrate external APIs, both language stacks) matching the 'several specific actions; minor gaps' anchor; not 5 because phrases like 'high-quality' and 'well-designed tools' are evaluative fluff rather than additional concrete capabilities, and not 3 because it goes beyond naming the domain with 1-2 actions.

4 / 5

Completeness

Quotes: 'Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools' (explicit what) and 'Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK)' (explicit when with concrete trigger phrases). Both what and when are explicitly stated with specific triggers, matching the top anchor; the when clause is concrete and scoped rather than weakly implied, so it is not 4.

5 / 5

Trigger Term Quality

Quotes: 'MCP', 'Model Context Protocol', 'MCP servers', 'integrate external APIs or services', 'FastMCP', 'Node/TypeScript (MCP SDK)'. Users building MCP servers would naturally say 'build an MCP server', 'FastMCP', or 'TypeScript MCP SDK', giving good keyword coverage; not 5 because natural variations like 'tool server', 'MCP tools', or 'expose an API to Claude' are missing, and not 3 because coverage clearly exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'MCP (Model Context Protocol) servers', 'building MCP servers to integrate external APIs or services'. This is a clear niche with distinct triggers — the MCP qualifier dominates, so generic API-integration or web-development skills are unlikely to fire on it. Minimal conflict risk; not 4 because the phrase 'integrate external APIs or services' is always bound to the MCP context, leaving only negligible overlap.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 10 missing

Warning

Total

15

/

16

Passed

Repository

databricks/devhub

Path

.agents/skills/mcp-builder/SKILL.md

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.