api-mcp-server

Generate an MCP server from a draft-spec.json or registry spec.

10|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/superluminar-io/pinky-promise --skill api-mcp-server-superluminar-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-mcp-server
Source: https://github.com/superluminar-io/pinky-promise/tree/main/skills/api-mcp-server
Command: npx skills add https://github.com/superluminar-io/pinky-promise --skill api-mcp-server-superluminar-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a production-ready MCP server from a pinky-promise spec, enabling services to be exposed as MCP tools immediately and without manual boilerplate.

Core Features & Use Cases

  • Auto-generates mcp-server.js per operation from the spec or registry.
  • Builds per-operation MCP tools with explicit input schemas.
  • Produces a ready-to-run package.json and setup instructions for Claude Code integration.
  • Supports environment-based service URL binding and standard HTTP bindings.
  • Example: Turn a service spec into a callable MCP tool suite within Claude Code.

Quick Start

Generate an MCP server for your service using the draft-spec.json or registry, then run npm install and start the server.

Frequently Asked Questions about api-mcp-server

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

FAQPage Schema
How do I generate an MCP server from an API spec for Claude Code?

You generate an MCP server by providing a pinky-promise draft-spec.json or registry spec. The tool translates operations into callable MCP tools with explicit input schemas, ready for immediate integration.

What is the best way to expose a service as MCP tools without manual boilerplate?

The best way to expose a service as MCP tools is using a pinky-promise spec to auto-generate a production-grade server. This enforces a deterministic code structure and outputs mcp-server.js without manual boilerplate.

How do I set up environment variables and HTTP bindings for an MCP server?

Environment variables and HTTP bindings are configured during generation. The tool supports environment-based service URL binding and standard HTTP bindings, translating spec operations into properly configured MCP tools.

Can I use a local draft-spec.json to create MCP tools for Claude Code?

Yes, you can use a local draft-spec.json to create MCP tools. The generator sources specs from a local draft-spec.json or registry, producing a ready-to-run package.json and setup instructions for Claude Code.

Does MCP server generation from pinky-promise specs validate inputs and error conditions?

Yes, MCP server generation from pinky-promise specs validates inputs and error conditions. It enforces a deterministic code structure while translating operations into MCP tools with proper HTTP bindings.