build-mcp-server

Design MCP servers with deployment, tool pattern, and authentication planning.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/victorjoshi9/content--1- --skill build-mcp-server-victorjoshi9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-mcp-server
Source: https://github.com/victorjoshi9/content--1-/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcp-server
Command: npx skills add https://github.com/victorjoshi9/content--1- --skill build-mcp-server-victorjoshi9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you plan and build an MCP server without choosing the wrong architecture too early, which prevents costly rewrites and integration mistakes.

Core Features & Use Cases

  • Deployment Guidance: Recommends the right delivery model for cloud APIs, local apps, filesystem access, and prototype tools.
  • Tool Design Strategy: Helps choose between one-tool-per-action and search-plus-execute patterns based on API size and usage.
  • Auth and Capability Planning: Covers API keys, OAuth, elicitation, resources, prompts, sampling, and other MCP server capabilities.
  • Use Case: Use it when wrapping a SaaS API for Claude, exposing a local desktop workflow, or deciding whether to ship remote HTTP, MCPB, or local stdio.

Quick Start

Use this skill to help me design the right MCP server for my use case by asking the deployment, tool, and auth questions first.

Frequently Asked Questions about build-mcp-server

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

FAQPage Schema
How do I design an MCP server architecture for a SaaS API?

To design an MCP server for a SaaS API, you must first determine the correct deployment model, tool design pattern, framework, and authentication approach to prevent costly rewrites and integration mistakes.

What is the best way to choose between remote HTTP, MCPB, and local stdio for an MCP server?

Choosing between remote HTTP, MCPB, and local stdio depends on your specific use case, such as wrapping a cloud API, exposing a local desktop workflow, or building a filesystem automation tool. Matching the deployment model to your use case prevents architectural mismatch.

How does tool design pattern selection work for a Claude-compatible MCP server?

Tool design pattern selection for a Claude-compatible MCP server involves choosing between a one-tool-per-action pattern and a search-plus-execute pattern based on the API size and expected usage.

Can I use OAuth and API keys for authentication in my MCP server?

Yes, you can use OAuth and API keys for authentication in an MCP server. Capability planning covers API keys, OAuth, elicitation, resources, prompts, and sampling to ensure secure access.

When should I use a search-plus-execute pattern instead of one-tool-per-action in MCP development?

You should use a search-plus-execute pattern in MCP development when wrapping large APIs where defining a single tool for every action becomes unmanageable.