HAPI MCP - AI-ready APIs

Convert OpenAPI v3 specifications into MCP servers using HAPI CLI. Supports local, Docker, and Cloudflare Workers deployment. Zero code required. Use when you need to expose API functionality as MCP tools or deploy API-based services to multiple hosting platforms.

Evaluate MCP servers for quality and reliability. Verify tool functionality, test error handling, generate tests, and assess response quality with no dependencies other than curl. Use this when validating MCP server implementations, testing OpenAPI-to-MCP conversions, or assessing API tool quality.

The shared plugin contract for the HAPI CLI. Consumed by the core CLI, first-party plugins, and third-party extensions.

Turn existing OpenAPI specs into MCP servers you can deploy, secure, and operate like real software with zero code needed, meaning, NO shadow code

Contract-driven MCP trip-booking demo, Jev/TypeSafe helps when the user's intent is clear but the wording is ambiguous

The HAPI MCP Server Registry Integration

OrcA - Orchestrator for APIs and Agents - MCPs Harness

Cloudflare Workers deployment for the HAPI CLI: deploy, login, status. Bundles the HAPI worker entrypoint.

OpenAPI-driven commands for the HAPI CLI: init, lint, list, serve.

Arazzo workflow validation and MCP serving for HAPI.

HAPI CLI — the core executable. Thin shell that discovers first-party and third-party plugins, routes commands, and provides a consistent UX across the HAPI stack.

HAPI MCP engine: Elysia server, MCP handlers, OAuth flows, swagger model, OpenAPI utilities, telemetry. Consumed by first-party plugins — not a user-facing CLI.

Telemetry / OpenTelemetry surface for the HAPI CLI. Opt-in/out, status, and flush controls.

Compile OpenAPI documents into deterministic HAPI capability graphs.