mcp-builder

Build MCP servers in Python or TypeScript with structured tool registration.

Updated Mar 1, 2017
One-click install
npx skills add https://github.com/TedTschopp/tedt.org --skill mcp-builder-tedtschopp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-builder
Source: https://github.com/TedTschopp/tedt.org/tree/main/.github/skills/mcp-builder
Command: npx skills add https://github.com/TedTschopp/tedt.org --skill mcp-builder-tedtschopp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

MCP server development for enabling LLMs to safely call external services via well-defined tools, with strong validation, transport choices, and error handling.

Core Features & Use Cases

  • Structured tool registration using the MCP SDKs (Python and TypeScript)
  • Clear input validation (Pydantic/Zod), robust error handling, and pagination-friendly responses
  • Practical guidance for building, testing, and deploying MCP servers across stdio and streamable HTTP transports
  • Real-world scenarios include API integration, data workflows, and automation tasks

Quick Start

Run the sample MCP server scaffold using the TypeScript or Python template and register a basic tool to verify end-to-end operation.

Frequently Asked Questions about mcp-builder

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

FAQPage Schema
How do I build an MCP server to let an LLM call external APIs?

To build an MCP server for external API integration, you use a structured framework with the Python (FastMCP) or Node/TypeScript SDK to define tools, apply input validation schemas, and configure stdio or HTTP transports.

How does tool registration work when creating MCP servers for LLMs?

Tool registration in MCP servers involves defining frontmatter-driven metadata and standardized tool annotations like readOnlyHint or destructiveHint to specify behavior, ensuring LLMs safely call external services via well-defined interfaces.

What is the best way to validate inputs for an MCP server tool?

The best way to validate MCP server tool inputs is using Pydantic for Python or Zod for TypeScript, providing strong validation schemas that ensure robust error handling and pagination-friendly responses for external service calls.

Can I use MCP SDKs with both Python and TypeScript for API integration?

Yes, MCP SDKs support both Python using FastMCP and Node/TypeScript using the MCP SDK, allowing you to build servers for API integration, tool orchestration, and transport configuration across multiple languages.

How do I configure transport for an MCP server using stdio or HTTP?

Configuring transport for an MCP server involves selecting between stdio and streamable HTTP transports during the building and deployment process to enable LLMs to communicate safely with your registered tools.

Why do I need standardized tool annotations like readOnlyHint in MCP servers?

Standardized tool annotations like readOnlyHint, destructiveHint, idempotentHint, and openWorldHint are needed in MCP servers to clearly communicate tool behavior characteristics to LLMs, ensuring safe and predictable external service execution.