MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Build agentic MCP servers using @mcpc/core by composing existing MCP tools.
$ npx skills add mcpc-tech/mcpc --skill mcpc-core -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mcpc-tech/mcpc mcpc-core --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/mcpc-tech/mcpc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/mcpc-core .claude/skills/mcpc-core && 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 "mcpc-core" agent skill from https://github.com/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-core into .claude/skills/mcpc-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcpc-core", 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/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-coreType 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 mcpc-tech/mcpc --skill mcpc-core -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mcpc-tech/mcpc mcpc-core --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mcpc-tech/mcpc.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/mcpc-core .agents/skills/mcpc-core && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mcpc-core" agent skill from https://github.com/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-core into .agents/skills/mcpc-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcpc-core", 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 mcpc-tech/mcpc --skill mcpc-core -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mcpc-tech/mcpc mcpc-core --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mcpc-tech/mcpc.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/mcpc-core .cursor/skills/mcpc-core && 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 "mcpc-core" agent skill from https://github.com/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-core into .cursor/skills/mcpc-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcpc-core", 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/mcpc-tech/mcpc.git --path .agents/skills/mcpc-core--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 mcpc-tech/mcpc --skill mcpc-core -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mcpc-tech/mcpc mcpc-core --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mcpc-tech/mcpc.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/mcpc-core .gemini/skills/mcpc-core && 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 "mcpc-core" agent skill from https://github.com/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-core into .gemini/skills/mcpc-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcpc-core", 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 mcpc-tech/mcpc mcpc-coreInstalls 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 mcpc-tech/mcpc --skill mcpc-core -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mcpc-tech/mcpc.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/mcpc-core .github/skills/mcpc-core && 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 "mcpc-core" agent skill from https://github.com/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-core into .github/skills/mcpc-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcpc-core", 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 mcpc-tech/mcpc --skill mcpc-core -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mcpc-tech/mcpc mcpc-core --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mcpc-tech/mcpc.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/mcpc-core .opencode/skills/mcpc-core && 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 "mcpc-core" agent skill from https://github.com/mcpc-tech/mcpc/tree/main/.agents/skills/mcpc-core into .opencode/skills/mcpc-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcpc-core", 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.
mcpc-coreBuild agentic MCP servers using @mcpc/core by composing existing MCP tools.
Mcpc Core is an agent skill from mcpc-tech/mcpc. Build agentic MCP servers using @mcpc/core by composing existing MCP tools. Use when creating, extending, or debugging MCPC agentic servers — including setting up compositions, choosing execution modes, writing plugins, loading skills, and connecting transports.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Build agentic-MCP servers by composing existing MCP tools. The licence is MIT.
Read from SKILL.md and the folder at commit 918ffef. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
denonpmpnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm and pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mcpc Core loads about 2.2k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 320 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.
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); files beside SKILL.md are not scanned.
The full file from mcpc-tech/mcpc at commit 918ffef, republished under its MIT licence (© mcpc-tech). 320 words, ~2,184 tokens.
.claude/skills/mcpc-core/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.@mcpc/core lets you compose existing MCP tools into agentic MCP tools. You
write a description that references tools via <tool> XML tags, and MCPC wires
everything up into a working MCP server.
# Deno (preferred in this repo)
deno add jsr:@mcpc/core
# npm
npm install @mcpc-tech/core
# pnpm (from JSR)
pnpm add jsr:@mcpc/coreimport { mcpc } from "@mcpc/core";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
const server = await mcpc(
[{ name: "my-agent", version: "1.0.0" }, { capabilities: { tools: {} } }],
[{
name: "file-agent",
description: `I help manage files.
Available tools:
<tool name="@wonderwhy-er/desktop-commander.read_file"/>
<tool name="@wonderwhy-er/desktop-commander.write_file"/>`,
deps: {
mcpServers: {
"@wonderwhy-er/desktop-commander": {
command: "npx",
args: ["-y", "@wonderwhy-er/desktop-commander@latest"],
transportType: "stdio",
},
},
},
}],
);
await server.connect(new StdioServerTransport());mcpc(serverConf, composeConf?, options?)| Param | Type | Description |
|---|---|---|
serverConf | [ServerMeta, ServerCapabilities] | Name/version + capabilities tuple |
composeConf | ComposeInput[] | Array of ComposeDefinition objects or .md file paths |
options | McpcOptions | Loader plugins + setup callback |
Returns Promise<ComposableMCPServer>.
ComposeDefinition{
name: string | null, // null = composition-only (no tool exposed)
description?: string, // Natural language + <tool> XML refs
manual?: string, // Progressive disclosure: long docs hidden behind man tool
deps?: MCPSetting, // Dependent MCP servers to connect
plugins?: (ToolPlugin | string)[], // Runtime plugins
options?: {
mode?: "agentic" | "ai_sampling" | "ai_acp", // default: "agentic"
maxSteps?: number, // default: 50
maxTokens?: number, // default: 128_000 (ai_sampling only)
samplingConfig?: SamplingConfig,
providerOptions?: { modelPreferences?: {...} }, // ai_sampling only
acpSettings?: { command, args, env, session, persistSession }, // ai_acp only
tracingEnabled?: boolean, // OpenTelemetry
refs?: ToolRefXml[],
}
}<tool> XML)In the description field, reference tools with XML tags:
<tool name="server.tool_name"/> — specific tool
<tool name="server.__ALL__"/> — all tools from a server
<tool name="server.tool" maxResultLength="2000"/> — truncate large results
<tool name="server.tool" hide/> — use internally, hide from public API
<tool name="server.tool" global/> — expose at top-level scopedeps.mcpServers)Three transport types:
// stdio
"my-server": { command: "npx", args: ["-y", "pkg@latest"], transportType: "stdio" }
// Streamable HTTP
"remote": { transportType: "streamable-http", url: "https://api.example.com/mcp/",
headers: { "Authorization": "Bearer ${TOKEN}" } }
// SSE
"sse-server": { transportType: "sse", url: "https://api.example.com/sse/" }| Mode | Description | Best For |
|---|---|---|
agentic | Fully autonomous, uses MCP sampling | Default; most flexible |
ai_sampling | Uses AI SDK streamText + MCP sampling provider | When you control the model |
ai_acp | AI SDK + ACP protocol for coding agents | Claude Code, Codex-style agents |
@mcpc/core/plugins)import {
createBashPlugin, // Add bash execution tool
createLargeResultPlugin, // Truncate/paginate large tool results
createSearchPlugin, // Add ripgrep-based search tool
createSkillsPlugin, // Lazy-load skill knowledge
} from "@mcpc/core/plugins";// In ComposeDefinition
plugins: [
createLargeResultPlugin({ maxSize: 8000 }),
createSkillsPlugin({ paths: [".agents/skills"] }),
createBashPlugin(),
"./my-plugin.ts?param=value", // File path with query params
];
// Or in mcpc() options (loader plugins, run before composition)
await mcpc(serverConf, composeConf, {
plugins: ["@mcpc/plugin-markdown-loader"],
});ToolPlugin)import type { ToolPlugin } from "@mcpc/core";
const myPlugin: ToolPlugin = {
name: "my-plugin",
// Mutate/filter tool descriptions at compose time
transformTool?: (tool: ComposedTool, ctx: TransformContext) => ComposedTool,
// Intercept inputs before execution
transformInput?: (args: unknown, ctx: BeforeToolExecuteContext) => unknown,
// Intercept outputs after execution
transformOutput?: (result: unknown, ctx: AfterToolExecuteContext) => unknown,
// Lifecycle hooks
onComposeStart?: (ctx: ComposeStartContext) => void,
onComposeEnd?: (ctx: ComposeEndContext) => void,
onFinalize?: (ctx: FinalizeContext) => void,
};createSkillsPlugin adds a {agent}__load-skill tool that lazy-loads skill
content:
createSkillsPlugin({
paths: [join(projectRoot, ".agents/skills")],
});Skills directory structure:
.agents/skills/
└── my-skill/
├── SKILL.md ← main instructions (loaded by default)
└── references/
└── api.md ← loaded via { skill, ref: "references/api.md" }Agent calls:
agent__load-skill({ skill: "my-skill" })
agent__load-skill({ skill: "my-skill", ref: "references/api.md" })Load agent definitions from .md files (requires
@mcpc/plugin-markdown-loader):
await mcpc(
[{ name: "server", version: "1.0.0" }, { capabilities: { tools: {} } }],
["./agents/my-agent.md"],
{ plugins: ["@mcpc/plugin-markdown-loader"] },
);Markdown format:
---
name: my-agent
deps:
mcpServers:
some-server:
command: npx
args: ["-y", "some-server"]
transportType: stdio
options:
mode: agentic
---
I am an agent that does X.
<tool name="some-server.tool"/>Register tools directly on the server before composition:
import { jsonSchema } from "@mcpc/core";
await mcpc(serverConf, composeConf, {
setup: async (server) => {
server.tool(
"my-tool",
"Description of tool",
jsonSchema({ type: "object", properties: { input: { type: "string" } } }),
async (args) => ({
content: [{ type: "text", text: `Got: ${args.input}` }],
}),
);
await server.addPlugin(myPlugin);
},
});transportType is required in every mcpServers entry — omitting it
causes a silent failure.name: null in ComposeDefinition skips creating the composed tool;
useful for composition-only (just wiring up deps + plugins).McpcOptions.plugins run before composition
(use for loaders). ComposeDefinition.plugins run after composition (use for
runtime transforms).hide vs global on <tool>: hide keeps a tool internal to the agent.
global exposes it at top-level without a namespace prefix.manual field: if set, description becomes a short summary and full
content is behind a man tool call — reduces initial context size.${VAR_NAME} syntax inside strings
in deps.mcpServers[*].headers — MCPC expands them at runtime.maxSteps default is 50 for ai_sampling/ai_acp modes — increase for
complex multi-step tasks.references/examples.md for complete working examples© mcpc-tech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in .agents/skills/mcpc-core of mcpc-tech/mcpc.
Open the folder on GitHubat commit 918ffef
Mcpc Core 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 |
|---|---|---|---|---|---|---|
| Mcpc Core this skillmcpc-tech/mcpc | 103 | — | ~2.2k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
mcpc-tech/mcpc
Creates presentation slides using Slidev with Markdown syntax.
mcpc-tech/mcpc
Release @mcpc/acp-ai-provider package for AI SDK v5 (0.1.x versions) from release-v5 branch.
mcpc-tech/mcpc
Upgrades mcpc package versions and their dependencies. An agent skill from mcpc-tech/mcpc.
Works with
Categories
Build agentic MCP servers using @mcpc/core by composing existing MCP tools. Mcpc Core is an agent skill from mcpc-tech/mcpc. Build agentic MCP servers using @mcpc/core by composing existing MCP tools.
Mcpc Core fits situations like: debugging MCPC agentic servers — including setting up compositions; choosing execution modes; writing plugins; connecting transports.
Run `npx skills add mcpc-tech/mcpc --skill mcpc-core -a claude-code`. Or copy the skill folder (.agents/skills/mcpc-core in mcpc-tech/mcpc) into .claude/skills/mcpc-core in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mcpc-tech/mcpc --skill mcpc-core -a codex`. Or copy the skill folder (.agents/skills/mcpc-core in mcpc-tech/mcpc) into .agents/skills/mcpc-core in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mcpc-tech/mcpc --skill mcpc-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcpc-core, .gemini/skills/mcpc-core, .github/skills/mcpc-core and .opencode/skills/mcpc-core in your project.
Going by SKILL.md and its folder, Mcpc Core needs the command-line tools its instructions call (deno, npm and pnpm). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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. Review the folder before installing.
Mcpc Core is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.7k 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 1.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Mcpc Core: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mcpc-tech (a GitHub organization) maintains it in mcpc-tech/mcpc, which has 103 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: mcpc-tech/mcpc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.