mcp-server-spec
Design an MCP server for a product — the tool surface, auth model, and safety boundaries that make it genuinely usable by AI agents. Use when asked to spec an MCP server, expose a product to agents, design tools for Claude or other MCP clients, or review why an existing MCP server performs badly. Produces a complete server spec: a small task-shaped toolset with agent-tested descriptions, auth and scoping decisions, error design, and an explicit not-exposed list.
npx skills add mohitagw15856/pm-claude-skills --skill mcp-server-spec --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MCP Server Spec Skill Every SaaS is shipping an MCP server; most dump their REST API as forty tools and wonder why agents flail. This skill designs the server as what it actually is: a *user interface for a non-human user* — few tools, task-shaped, with descriptions written for a model deciding under uncertainty. ## What This Skill Produces - A **toolset design**: 3-10 tools mapped to agent *tasks*, not API endpoints - **Per-tool specs**: name, description (the routing surface), parameters, returns, error behaviour - **Auth & scoping decisions**: how credentials flow, what a token can never do - An explicit **not-exposed list** with reasons — the most load-bearing section - A **test plan**: the agent-eval loop that proves the toolset works ## Required Inputs Ask for (if not already provided): - **The product** and what users hire it for (the top 5 jobs, not the feature list) - **The existing API surface** (endpoints or capability list) if one exists - **Who the agent acts for** — the end user's own account? a service account? multi-tenant? - **The riskiest actions** the product supports (deletes, sends, payments, permission changes) ## Design Method 1. **Start from agent tasks, n
- What This Skill Produces
- Required Inputs
- Design Method
- Output Format
- MCP Server Spec: [product]
- Quality Checks
- Anti-Patterns
What does the mcp-server-spec skill do?
Design an MCP server for a product — the tool surface, auth model, and safety boundaries that make it genuinely usable by AI agents. Use when asked to spec an MCP server, expose a product to agents, design tools for Claude or other MCP clients, or review why an existing MCP server performs badly. Produces a complete server spec: a small task-shaped toolset with agent-tested descriptions, auth and scoping decisions, error design, and an explicit not-exposed list.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill mcp-server-spec --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.