What problem does it solve?
This Skill helps you design the right kind of MCP server before you write code, avoiding costly rewrites caused by choosing the wrong deployment model, tool shape, or authentication approach.
Core Features & Use Cases
- Use-Case Discovery: Clarifies what the server connects to, who will use it, how many actions it exposes, and whether it needs interactive input or rich UI.
- Architecture Recommendation: Recommends remote HTTP, MCPB, local stdio, or MCP app patterns based on the integration scenario.
- Implementation Guidance: Helps with tool design, framework selection, auth planning, and use of MCP primitives like resources, prompts, elicitation, and sampling.
- Real-World Example: A developer wrapping a SaaS API can use this Skill to choose a remote MCP server, decide between one-tool-per-action or search-and-execute, and scaffold the server with the right guardrails.
Quick Start
Use this skill to describe your integration target, users, and desired actions, and then follow its recommendation for the best MCP server design.