agentleFS
Sign inStart free
techsaurabh-394techsaurabh-394/claude-skills/skills/mcp-server-builder/SKILL.md

mcp-server-builder

Skill3 starsChanged 11 days agoMITView on GitHub

Scaffold a Model Context Protocol (MCP) server in TypeScript with typed tools, input validation and a test checklist. Use when the user wants to expose an API, database or internal tool to an AI assistant through MCP.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 4

    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:

    Prefer small, single-purpose tools with explicit descriptions.

    line 10
  2. Distinctive:

    Keep responses compact; return only the fields the model needs.

    line 13
  3. Distinctive:

    Check the current SDK documentation before finalising.

    line 32
  4. Distinctive:

    Test checklist: each tool with valid input, invalid input, empty result, upstream failure

    line 38

“Common” is measured: kept by at least 6 in 10 of the 11 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 Builder

Process

  1. Clarify the system being exposed and list 3-7 tools (verbs the model can call). For each tool: name, one-line purpose, input schema, output shape, side effects (read-only vs writes).
  2. Prefer small, single-purpose tools with explicit descriptions. Descriptions are what the model reads to choose a tool.
  3. Validate every input with a schema. Return errors as readable text, never stack traces.
  4. Mark destructive tools clearly in the description and require explicit parameters (no implicit "delete all").
  5. Keep responses compact; return only the fields the model needs.

Starter (TypeScript, @modelcontextprotocol/sdk + zod)

import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({ name: "example-server", version: "1.0.0" });

server.tool(
  "add_numbers",
  "Add two numbers and return the sum.",
  { a: z.number(), b: z.number() },
  async ({ a, b }) => ({ content: [{ type: "text", text: String(a + b) }] })
);

await server.connect(new StdioServerTransport());

Check the current SDK documentation before finalising; the API evolves.

Deliverables

  • Project layout (src/index.ts, src/tools/*.ts, package.json, tsconfig.json)
  • Tool table (name, inputs, outputs, side effects)
  • Claude Desktop / client config snippet to register the server
  • Test checklist: each tool with valid input, invalid input, empty result, upstream failure
  • Security notes: secrets via env vars, least-privilege credentials, no arbitrary shell or SQL execution

Download now (ZIP)

  • Other versions15 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use agent-designer, env-secrets-manager and 1 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.
    • Arnav-0Skill

      agent-designer

      Use when the user asks to design multi-agent systems, create agent architectures, define agent communication patterns, or build autonomous agent workflows.

      Also in 4 projects that use this

    • Arnav-0Skill

      env-secrets-manager

      Env & Secrets Manager

      Also in 3 projects that use this

    • JeffallanSkill

      rag-architect

      Designs and implements production-grade RAG systems by chunking documents, generating embeddings, configuring vector stores, building hybrid search pipelines, applying reranking, and evaluating retrieval quality. Use when building RAG systems, vector databases, or knowledge-grounded AI applications requiring semantic search, document retrieval, context augmentation, similarity search, or embedding-based indexing.

      Also in 3 projects that use this

  • In this repository2 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free