MCP Server Builder
alirezarezvani/claude-skills
Design and ship production-ready MCP (Model Context Protocol) servers from OpenAPI contracts instead of hand-written tool wrappers.
Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports.
Install MCP Server Builder
$ npx skills add borghei/Claude-Skills --skill mcp-server-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills mcp-server-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/mcp-server-builder .claude/skills/mcp-server-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mcp-server-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builder into .claude/skills/mcp-server-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-server-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill mcp-server-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills mcp-server-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/mcp-server-builder .agents/skills/mcp-server-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mcp-server-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builder into .agents/skills/mcp-server-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-server-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill mcp-server-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills mcp-server-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/mcp-server-builder .cursor/skills/mcp-server-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mcp-server-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builder into .cursor/skills/mcp-server-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-server-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/mcp-server-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill mcp-server-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills mcp-server-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/mcp-server-builder .gemini/skills/mcp-server-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mcp-server-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builder into .gemini/skills/mcp-server-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-server-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills mcp-server-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill mcp-server-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/mcp-server-builder .github/skills/mcp-server-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mcp-server-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builder into .github/skills/mcp-server-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-server-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill mcp-server-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills mcp-server-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/mcp-server-builder .opencode/skills/mcp-server-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mcp-server-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/mcp-server-builder into .opencode/skills/mcp-server-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-server-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mcp-server-builder- GitHub stars
- 874
- Token cost
- ~1.9k tokens
- SKILL.md length
- 819 words
- Files
- 10 (incl. scripts, references)
- Skills in repo
- 364
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports.
- Exposing APIs to AI agents
- SKILL.md covers Overview, Keywords, Core Capabilities and When to Use, plus 5 more sections
- Runs Python scripts from its folder
- Building tool servers
What it does
MCP Server Builder is an agent skill from borghei/Claude-Skills. Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports. Use when exposing APIs to AI agents, building tool servers, converting OpenAPI to MCP, or creating MCP integrations.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `references/server-implementation.md`, `references/streaming-batch-and-computer-use.md` and `references/testing-and-troubleshooting.md`).
It sits in Agent Workflows, covering MCP servers, OpenAPI specifications and Structured output and tool calling. It works with Model Context Protocol, OpenAPI and TypeScript. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Exposing APIs to AI agents
- Building tool servers
- Converting OpenAPI to MCP
- Creating MCP integrations
Example prompts
- “/mcp-server-builder”
Requirements
- Python 3
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
MCP Server Builder loads about 1.9k tokens when it runs, and up to ~9.6k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 819 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 819 words, ~1,949 tokens.
Download SKILL.mdSave it as
.claude/skills/mcp-server-builder/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- mcp-server-builder
- description
- Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports. Use when exposing APIs to AI agents, building tool servers, converting OpenAPI to MCP, or creating MCP integrations.
- license
- MIT + Commons Clause
- metadata.version
- 1.2.0
- metadata.author
- borghei
- metadata.category
- engineering
- metadata.domain
- ai-integration
- metadata.tier
- POWERFUL
- metadata.updated
- 2026-06-29
- metadata.frameworks
- mcp-sdk, typescript, python, openapi
MCP Server Builder
Tier: POWERFUL Category: Engineering / AI Integration Maintainer: Claude Skills Team
Overview
Design and ship production-ready MCP (Model Context Protocol) servers from API contracts. Covers tool definition best practices, resource providers, prompt templates, OpenAPI-to-MCP conversion, TypeScript and Python server implementations, transport selection (stdio, SSE, StreamableHTTP), authentication patterns, testing strategies, and deployment configurations. Treats schema quality and tool discoverability as first-class concerns.
Keywords
MCP, Model Context Protocol, MCP server, tool definition, resource provider, prompt template, stdio transport, SSE transport, OpenAPI to MCP, AI tool server, Claude tools
Core Capabilities
- Tool design & schema quality — verb-noun naming, description engineering, typed input schemas, LLM-friendly output formatting
- Server implementation — TypeScript (
@modelcontextprotocol/sdk) and Python (mcp[cli]) servers; tool/resource/prompt registration; structured error handling; logging, auth, and rate-limit middleware - Transport & deployment — stdio (local/CLI), SSE (web), StreamableHTTP (production), Docker containerization, health checks, graceful shutdown
- Testing & validation — schema validation, MCP Inspector integration tests, contract/snapshot tests, load testing for remote servers
When to Use
- Exposing an internal REST API to Claude, Cursor, or other MCP clients
- Replacing brittle browser automation with typed tool interfaces
- Building a shared MCP server for multiple teams and AI assistants
- Converting an OpenAPI spec into MCP tools automatically
- Creating domain-specific tool servers (database, monitoring, deployment)
Clarify First
Before building the server, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Source contract — the OpenAPI spec or API to expose, or whether building tools from scratch (the input the tool definitions and conversion derive from)
- Language — TypeScript (
@modelcontextprotocol/sdk) or Python (mcp[cli]) (sets the server implementation generated) - Transport — stdio (local/CLI), SSE (web), or StreamableHTTP (production) (drives transport, auth, and deployment patterns)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/tool-schema-design.md — naming conventions, description engineering template, and input schema best practices. Read first when defining any tool, since description quality drives LLM tool selection.
- references/server-implementation.md — complete TypeScript and Python server code (tools, resources, prompts) plus the OpenAPI-to-MCP conversion rules and script. Read when writing the server.
- references/transport-and-deployment.md — client configuration (
claude_desktop_config.jsonfor stdio and remote) and the tool versioning strategy. Read when connecting clients or planning releases. - references/testing-and-troubleshooting.md — schema validation function, MCP Inspector commands, common pitfalls, best practices, troubleshooting table, and success criteria. Read when validating, hardening for production, or diagnosing failures.
- references/streaming-batch-and-computer-use.md — progress/streaming and cancellation for long-running tools, wrapping computer-use/browser/desktop actions (granularity, returning state, safety gates), and batch-friendly tool design (arrays, idempotency, partial-failure results, pagination). Read when a tool runs long, drives a live surface, or processes many items.
Show full SKILL.md (376 more words)Show less
Common Patterns
- Streaming long-running tools — when a call routinely exceeds a few seconds (builds, crawls, automation), emit throttled progress updates with a stable correlation handle, stream semantically whole chunks ending in an explicit terminal signal, and honor cancellation by aborting the real work and cleaning up sessions. The final response must stand alone. See
references/streaming-batch-and-computer-use.md. - Batch-friendly tools — when an operation is naturally repeated, accept a bounded array instead of forcing one chatty call per item; make operations idempotent (or take an idempotency key) and return per-item success/failure results so the agent retries only what failed. List/read tools must paginate with a documented cap and a cursor. Run
scripts/tool_schema_linter.pyto flag chatty single-item tools and missing pagination. - Computer-use via MCP — expose intent-level actions (
navigate,click,read_page) rather than raw pixel primitives, return current observable state (text-first, screenshots only when layout matters), and gate destructive/irreversible actions behind aconfirm/dry_runparam scoped to an allowlist with secrets redacted. For the automation engine itself, see thecomputer-use-automationskill.
Scope & Limitations
This skill covers:
- Designing tool schemas, resource providers, and prompt templates for MCP servers
- Implementing servers in TypeScript (
@modelcontextprotocol/sdk) and Python (mcp[cli]) - Transport selection and client configuration (stdio, SSE, StreamableHTTP)
- OpenAPI-to-MCP conversion patterns and testing strategies
This skill does NOT cover:
- Building MCP clients or custom LLM orchestration layers — see
engineering/agent-workflow-designer - Designing multi-agent systems that consume MCP tools — see
engineering/agent-designer - API design itself (REST conventions, endpoint naming, versioning) — see
engineering/api-design-reviewer - Infrastructure provisioning, container orchestration, or CI/CD pipelines for deploying MCP servers — see
engineering/ci-cd-pipeline-builder
Integration Points
| Skill | Integration | Data Flow |
|---|---|---|
engineering/api-design-reviewer | Review the underlying REST API before converting it to MCP tools | OpenAPI spec → API review findings → refined spec → MCP conversion |
engineering/api-test-suite-builder | Generate integration tests for the HTTP endpoints that MCP tools wrap | MCP tool definitions → endpoint mapping → test suite generation |
engineering/agent-designer | Design agents that consume the MCP tools this skill produces | MCP tool schemas → agent tool inventory → agent behavior design |
engineering/observability-designer | Add structured logging, tracing, and metrics to MCP server handlers | MCP server code → instrumentation plan → logging/tracing middleware |
engineering/ci-cd-pipeline-builder | Automate build, test, and deploy pipelines for MCP server releases | MCP server repo → pipeline config → automated deploy to staging/prod |
engineering/env-secrets-manager | Manage API keys, database credentials, and tokens used in MCP server configs | MCP server env vars → secrets audit → secure injection patterns |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (scripts, references) in engineering/mcp-server-builder of borghei/Claude-Skills.
- SKILL.md
- references/server-implementation.md
- references/streaming-batch-and-computer-use.md
- references/testing-and-troubleshooting.md
- references/tool-schema-design.md
- references/transport-and-deployment.md
- scripts/openapi_converter.py
- scripts/server_scaffolder.py
- scripts/tool_linter.py
- scripts/tool_schema_linter.py
Open the folder on GitHubat commit c9a1487
Compare with similar skills
MCP Server Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| MCP Server Builder this skillborghei/Claude-Skills | 874 | — | ~1.9k | Automated safety check: Pass | MIT | |
| MCP Server Builderalirezarezvani/claude-skills | 28k | — | ~985 | Automated safety check: Pass | MIT | |
| Generate MCP Servertrycompai/comp | 2k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| PR Reviewconfluentinc/mcp-confluent | 167 | — | ~4.6k | Automated safety check: Notes | MIT | |
| Frontmcp Developmentagentfront/frontmcp | 146 | — | ~11k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Generate MCP Server
trycompai/comp
A skill your agent uses when generating an MCP server from an OpenAPI spec with Speakeasy.
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
PR Review
confluentinc/mcp-confluent
Reviews pull requests for the Confluent MCP server. An agent skill from confluentinc/mcp-confluent.
Frontmcp Development
agentfront/frontmcp
A skill your agent uses when building any FrontMCP server component other than a tool (for tools, use create-tool).
MCP Server Builder with mcp-use
mcp-use/mcp-use
Builds, modifies, debugs, migrates and verifies TypeScript MCP servers and MCP Apps with the mcp-use framework, treating the installed package's types as the source of truth.
More from borghei/Claude-Skills
All 364 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Works with
Categories
Questions about MCP Server Builder
What does MCP Server Builder do?
Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports. MCP Server Builder is an agent skill from borghei/Claude-Skills. Build MCP (Model Context Protocol) servers with tool definitions, resource providers, prompt templates, and transports.
When should I use MCP Server Builder?
MCP Server Builder fits situations like: exposing APIs to AI agents; building tool servers; converting OpenAPI to MCP; creating MCP integrations.
How do I install MCP Server Builder in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill mcp-server-builder -a claude-code`. Or copy the skill folder (engineering/mcp-server-builder in borghei/Claude-Skills) into .claude/skills/mcp-server-builder in your project. Claude Code loads it when a task matches its description.
How do I install MCP Server Builder in Codex?
Run `npx skills add borghei/Claude-Skills --skill mcp-server-builder -a codex`. Or copy the skill folder (engineering/mcp-server-builder in borghei/Claude-Skills) into .agents/skills/mcp-server-builder in your project. Codex loads it when a task matches its description.
Can I use MCP Server Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill mcp-server-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-server-builder, .gemini/skills/mcp-server-builder, .github/skills/mcp-server-builder and .opencode/skills/mcp-server-builder in your project.
What does MCP Server Builder need to run?
Going by SKILL.md and its folder, MCP Server Builder needs Python for the scripts in its folder. Our summary lists: Python 3; Docker.
Does MCP Server Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is MCP Server Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does MCP Server Builder use?
MCP Server Builder is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does MCP Server Builder use?
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.6k tokens, read only when the agent opens those files.
What are the alternatives to MCP Server Builder?
Skills that share tags, products or a category with MCP Server Builder: MCP Server Builder (alirezarezvani/claude-skills, 28k stars), Generate MCP Server (trycompai/comp, 2k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and PR Review (confluentinc/mcp-confluent, 167 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains MCP Server Builder?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.