HavenSkills

mcp-builder skill

By Anthropic

Design and test an MCP server that exposes an external service through clearly described tools.

Install this skill

npx skills add anthropics/skills --skill mcp-builder

Run the command from your project directory. If your client is already running, reload it and confirm the skill is available before trying the example below.

Source repo

Ask your agent to install the skill
Install mcp-builder from anthropics/skills in this project. Show me the destination folder and report any dependencies the source lists.

Install for your agent

Run the command for your client from your project directory.

Claude Code
npx skills add anthropics/skills --skill mcp-builder -a claude-code
Codex
npx skills add anthropics/skills --skill mcp-builder -a codex
Cursor
npx skills add anthropics/skills --skill mcp-builder -a cursor
GitHub Copilot
npx skills add anthropics/skills --skill mcp-builder -a github-copilot

How to use mcp-builder

Start with one bounded service operation and define inputs, expected outputs, and recoverable error behavior before adding more tools.

Example prompt and what to check

Design a read-only MCP tool that searches a documentation API. Include pagination behavior and a sample test using mock data.

Acceptance check Try a valid query, an empty response and a failed request. Confirm each result gives the client enough information to continue.

What the upstream guide covers

The upstream guide covers planning, implementing, reviewing and evaluating an MCP integration. It points to separate references for Python and TypeScript implementations.

HavenSkills workflow check

No workflow check recorded yet. Use the sample task above to make your own check in your client.

Review methodology and recorded checks

Requirements, permissions and limits

Authentication and data access depend on the service. Keep credentials outside prompts and fixtures.

Author
Anthropic
Skill source
SKILL.md

Frequently asked questions

Can I use Python or TypeScript?

The upstream guide covers both approaches. Choose the stack that fits your deployment and follow the current SDK documentation.