build-mcp-server

Orchestrate MCP server design and deployment for Claude integrations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interrogate the user and align on a clear MCP server design and deployment plan, reducing ambiguity and rework for Claude-integrated servers.

Core Features & Use Cases

  • Phase-based discovery to decide between Remote HTTP, MCPB, or local stdio deployment.
  • Tool-pattern selection strategy and handoff to specialized skills (one-per-action vs. search + execute).
  • End-to-end scaffolding and design brief generation to accelerate downstream implementation.

Quick Start

Begin by asking the user about their MCP server use case and deployment constraints, then recommend an execution path.

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 and deploy an MCP server for Claude integrations?

To design and deploy an MCP server for Claude, use a phase-based discovery process to choose between remote HTTP, MCPB, or local stdio deployment, select tool patterns, and generate a design brief for downstream implementation.

What is the difference between remote HTTP, MCPB, and local stdio MCP server deployments?

Remote HTTP, MCPB, and local stdio are distinct MCP server deployment models. Your choice depends on specific deployment constraints and use cases, determined through a phase-driven discovery process to ensure the correct architecture is selected.

How do I choose a tool-pattern selection strategy for my MCP server?

Choosing a tool-pattern selection strategy for an MCP server involves deciding between a one-per-action approach and a search plus execute model. This decision is made during the design phase before handing off to specialized skills.

Can I scaffold an MCP server architecture before writing the implementation code?

Yes, you can scaffold an MCP server architecture before implementation. The skill generates an end-to-end design brief and scaffolding plan, accelerating downstream coding by enforcing phase-driven questioning and clear handoff workflows.

What deployment constraints should I consider when building an MCP server?

When building an MCP server, consider deployment constraints like remote HTTP, MCPB, or local stdio requirements. Interrogating these constraints during discovery reduces ambiguity and rework for Claude-integrated servers.