mcp-api-build

Design OpenAPI-first REST APIs and convert endpoints into MCP primitives.

3|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/qwwiwi/agentos-skills-public --skill mcp-api-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-api-build
Source: https://github.com/qwwiwi/agentos-skills-public/tree/main/skills/mcp-api-build
Command: npx skills add https://github.com/qwwiwi/agentos-skills-public --skill mcp-api-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes guesswork and production risk when designing REST APIs and MCP servers by enforcing a consistent, standards-based workflow from domain modeling to secure deployment.

Core Features & Use Cases

  • API-first design with OpenAPI: Produces a complete OpenAPI spec before implementation to prevent contract drift.
  • REST → MCP conversion: Maps REST endpoints into MCP primitives (tools/resources/prompts) with naming and output-shape conventions.
  • Production readiness & security auditing: Includes checks for anti-patterns, pagination, idempotency, ETags, error formats, and secure deployment practices.
  • Three supported build paths: REST from scratch, MCP wrapping an existing REST API, or designing both together.

Quick Start

Use mcp-api-build to design and implement a REST API plus an MCP server for a new feature by following the REST-first workflow and then layering MCP tools/resources on top.

Frequently Asked Questions about mcp-api-build

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

FAQPage Schema
How do I convert a REST API to MCP server primitives?

Converting a REST API to MCP involves mapping existing endpoints into MCP tools, resources, and prompts using naming and structured JSON output conventions aligned with the MCP specification.

What is OpenAPI-first design and how does it prevent contract drift?

OpenAPI-first design produces a complete OpenAPI specification before implementation, establishing a strict contract that prevents discrepancies between API documentation and actual endpoint behavior during development.

How do I audit my REST API architecture for production readiness and anti-patterns?

Auditing REST API architecture for production readiness involves checking for anti-patterns, validating pagination, ensuring idempotency, standardizing error formats, and verifying ETags for conditional requests before deployment.

Can I design a new REST API and an MCP server together from scratch?

Yes, you can design a new REST API and an MCP server together by following a REST-first workflow to establish the OpenAPI contract and then layering MCP tools and resources on top of the endpoints.

What security and validation checks are needed for production REST API deployment?

Production REST API deployment requires security and validation checks covering pagination, error consistency, idempotency, conditional requests, and strict adherence to REST conventions to ensure secure and reliable operations.