agentleFS
LucfaceLucface/claude-skills/skills/mcp-builder/SKILL.md

mcp-builder

Skill1 starsChanged 3 days agoMITView on GitHub

Builds MCP (Model Context Protocol) servers for API integration. Guides the full development lifecycle from research to evaluation.

  • Reads credentials

188 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • ComposioHQSkill

    codebase-migrate

    Run large codebase migrations and multi-file refactors. Uses the Composio CLI to coordinate issue tracking, batched PRs, and CI verification while the agent executes the transforms locally across hundreds of files.

    Also in 5 projects that use this

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 projects that use this

  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 26 projects that use this

  • AnthropicSkill

    academy-guide

    Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

    Also in 8 projects that use this

  • +2 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test with MCP Inspector

    line 24
  2. Distinctive:

    Create 10 complex, realistic test questions

    line 28
  3. Distinctive:

    Verify LLMs can effectively use your server

    line 29
  4. Distinctive:

    Before implementing, use the package-search MCP to research SDK patterns:

    line 84
  5. Distinctive:

    Read-only (doesn't modify external state)

    line 140

“Common” is measured: kept by at least 6 in 10 of the 171 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MCP Server Development

Build Model Context Protocol servers that enable language models to interact with external services.

Four-Phase Approach

Phase 1: Deep Research & Planning

  • Study MCP design principles and protocol documentation
  • Select tech stack (TypeScript recommended)
  • Analyze target API thoroughly
  • Plan tool organization

Phase 2: Implementation

  • Project setup with proper dependencies
  • Core infrastructure (auth, error handling)
  • Individual tools with schemas and descriptions

Phase 3: Review & Testing

  • Code quality verification
  • Test with MCP Inspector
  • Error handling validation

Phase 4: Evaluation

  • Create 10 complex, realistic test questions
  • Verify LLMs can effectively use your server

Project Setup (TypeScript)

mkdir my-mcp-server && cd my-mcp-server
bun init
bun add @modelcontextprotocol/sdk zod
// src/index.ts
import { Server } from '@modelcontextprotocol/sdk/server/index.js';
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';

const server = new Server(
  { name: 'my-server', version: '1.0.0' },
  { capabilities: { tools: {} } }
);

// Define tools
server.setRequestHandler('tools/list', async () => ({
  tools: [
    {
      name: 'my_tool',
      description: 'Does something useful',
      inputSchema: {
        type: 'object',
        properties: {
          param: { type: 'string', description: 'Input parameter' }
        },
        required: ['param']
      }
    }
  ]
}));

server.setRequestHandler('tools/call', async (request) => {
  const { name, arguments: args } = request.params;

  if (name === 'my_tool') {
    // Implement tool logic
    return { content: [{ type: 'text', text: 'Result' }] };
  }

  throw new Error(`Unknown tool: ${name}`);
});

// Start server
const transport = new StdioServerTransport();
await server.connect(transport);

Research with Package Search MCP

Before implementing, use the package-search MCP to research SDK patterns:

# Find how the official MCP SDK structures servers
package_search_hybrid("@modelcontextprotocol/sdk server setup patterns", registry="npm")

# Look at real tool implementations
package_search_grep("setRequestHandler.*tools/call", package="@modelcontextprotocol/sdk", registry="npm")

This grounds your implementation in real source code rather than hallucinated patterns.

Key Design Principles

Tool Naming: Consistent, action-oriented

  • Good: github_create_issue, slack_send_message
  • Bad: doThing, handler1

Error Messages: Provide specific suggestions

throw new Error(
  `Repository not found: ${repo}. ` +
  `Check that the repository exists and you have access. ` +
  `Try: gh repo view ${repo}`
);

Balance Coverage: Combine comprehensive API endpoint coverage with specialized workflow tools.

Input Validation with Zod

import { z } from 'zod';

const CreateIssueSchema = z.object({
  repo: z.string().describe('Repository in owner/name format'),
  title: z.string().min(1).describe('Issue title'),
  body: z.string().optional().describe('Issue body in markdown'),
  labels: z.array(z.string()).optional().describe('Labels to apply')
});

// In tool handler
const params = CreateIssueSchema.parse(args);

Testing with MCP Inspector

bun run build
npx @modelcontextprotocol/inspector dist/index.js

Evaluation Questions

Each evaluation question must be:

  • Independent (no dependencies on other questions)
  • Read-only (doesn't modify external state)
  • Complex enough to require multiple tool calls
  • Realistic (matches actual use cases)
  • Verifiable (single clear answer)
  • Temporally stable (answer doesn't change)

Example:

"Find all open issues in repo X labeled 'bug' and summarize their common themes"

Claude Code Integration

Add to ~/.claude/claude_desktop_config.json:

{
  "mcpServers": {
    "my-server": {
      "command": "node",
      "args": ["/path/to/dist/index.js"],
      "env": {
        "API_KEY": "your-key"
      }
    }
  }
}

Source

Adapted from https://github.com/anthropics/skills (Apache-2.0, Copyright 2026 Anthropic, PBC.). Changed for this repo by Lucas Cooper-Bey in 2026: paraphrased, keeping the same four phases in the same order.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.