{
  "markdown": "# HAPI MCP – Headless API for Model Context Protocol\n\n**Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.**\n\nHAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.\n\n## Key Features\n\n- **No rewrites:** Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.\n- **Faster time-to-value:** Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.\n- **Reduced risk:** Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.\n- **Scales with you:** [runMCP](https://run.mcp.com.ai) delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.\n- **Deterministic orchestration:** OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.\n- **Vendor-neutral:** Works with any MCP client: ChatGPT, Claude, [QBot](https://qbot.mcp.com.ai), [chatMCP](https://chat.mcp.com.ai). OAS + MCP + Arazzo stay portable.\n\n## How It Works\n\n1. **Pick your API spec**\n   - OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.\n   - Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.\n\n2. **Run a single command**\n   - One simple CLI command transforms your API into a usable MCP Server.\n   - No complex setup, zero configuration, works anywhere, cross-platform.\n\n3. **Use instantly**\n   - Your API is now ready as a tool, AI agent, or testing interface.\n   - MCP server ready, AI agent compatible, testing interface, developer experience friendly.\n\n## Visual Pipeline\n\n```\nAPI Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients\n```\n\n```\n[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]\n       (Your API)         →   (Transform)   →   (Usable Tool)\n                                                 ↑          ↑\n                                                 |          |\n                                          [ ChatGPT ]  [ runMCP ]\n                                          [ Claude  ]  [ OrcA   ]\n                                          [ QBot    ]  [ chatMCP]\n                                          [ Agents  ]\n```\n\n## Who Wins With HAPI\n\n- **Executives:** Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.\n- **Architects & PMs:** Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.\n- **Engineers & Ops:** Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.\n\n## Your Stack, Already Wired\n\n- [**HAPI Server:**](https://hapi.mcp.com.ai) Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.\n- [**runMCP:**](https://run.mcp.com.ai) Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.\n- [**QBot:**](https://qbot.mcp.com.ai) CLI TUI for power users to interact with MCP tools directly from terminal or scripts.\n- [**chatMCP:**](https://chat.mcp.com.ai) Conversational client that speaks MCP natively for support, ops, and internal assistants.\n- [**OrcA:**](https://orca.mcp.com.ai) Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.\n- **Agents:** Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.\n\n## Demos\n\n- [Playlist with demos](https://www.youtube.com/playlist?list=PL7wYqDMFQYFOZuB1nNOfisbVzb1uHw1fz)\n- New [HAPI MCP YT Channel](https://youtube.com/@hapi-mcp) with demos API-First and MCP\n\n## Documentation\n\n- [Explore the Docs](https://docs.mcp.com.ai)\n- [See HAPI Server](https://hapi.mcp.com.ai)\n\n## FAQ\n\n- **Do we need to rewrite our services?**  \n  No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.\n\n- **Is this just another MCP server?**  \n  It’s the **Headless API** model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.\n\n- **Which clients can consume the tools?**  \n  Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.\n\n- **How do we keep control and compliance?**  \n  Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; **no shadow logic**.\n\n- **What about security and privacy?**  \n  Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.\n\n- **How fast can we get started?**  \n  You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.\n\n## Get Started\n\n1. Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases\n2. Transform your OpenAPI spec into an MCP server with a single command:\n   ```bash\n   hapi serve path/to/your/swagger.json --headless\n   ```\n3. Start using your MCP tools with any compatible client!\n\n4. Explore the [documentation](https://docs.mcp.com.ai) for advanced usage and best practices.\n\n## Contributing\n\nContributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp\n\n## License\n\nHAPI MCP is licensed under the MIT License. See LICENSE for details.",
  "bytes": 5629,
  "sha": "79a64c63d13cd08ba1e833366f2f577e2929d73421d7c5f97a3de5aeb00b58cf",
  "repo_slug": "la-rebelion/hapimcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_com_mcp_strava_9a089d7a/readme"
}