design-mcp-server

Design MCP server tool surfaces and service layers from goals to primitives.

148|28|Updated Mar 20, 2025
One-click install
npx skills add https://github.com/cyanheads/mcp-ts-core --skill design-mcp-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-mcp-server
Source: https://github.com/cyanheads/mcp-ts-core/tree/main/skills/design-mcp-server
Command: npx skills add https://github.com/cyanheads/mcp-ts-core --skill design-mcp-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document the overall design for a new MCP server, including user goals, tool primitives, safety considerations, and architecture guidance, before scaffolding.

Core Features & Use Cases

  • Guides the design of the MCP server surface: tools, resources, prompts, and safety guards.
  • Helps map user goals to domain operations and MCP primitives (tools, resources, prompts).
  • Produces a design doc and artifacts that drive implementation and evaluation.

Quick Start

Describe the MCP server domain and goals to trigger a design-session that outputs a complete design document.

Frequently Asked Questions about design-mcp-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design the tool surface for a new MCP server?

To design an MCP server tool surface, map user goals to domain operations and MCP primitives like tools, resources, and prompts. This process structures the service layer and defines safety guards before implementation begins.

What is the best way to plan MCP server safety constraints and architecture?

Planning MCP server safety constraints requires mapping user goals to domain operations and enforcing a structured design process. This approach defines safety guards, tool taxonomy, and architecture guidance within a comprehensive design document.

How do I map user goals to MCP primitives when building a server?

Mapping user goals to MCP primitives involves analyzing domain operations and categorizing them into tools, resources, and prompts. This structured design process ensures the server surface aligns with intended user workflows and safety considerations.

Do I need a design document before scaffolding an MCP server?

A design document is needed before scaffolding an MCP server to establish architecture guidance, tool primitives, and safety considerations. This pre-scaffolding planning produces artifacts that drive implementation and evaluation.

Can I use this structured design process for major feature expansions to an existing MCP server?

This structured design process is applicable for major feature expansions to an existing MCP server. It guides planning from goals to primitives, ensuring new tools, resources, and safety guards integrate properly.

What deliverables should I expect from an MCP server design session?

Deliverables from an MCP server design session include a complete design document and artifacts. These outputs define the tool taxonomy, domain primitives, safety constraints, and architecture guidance needed to drive implementation.