PluginBench
MCP Server
Active
MIT

Petstore MCP Server MCP Server

ai.com.mcp/petstore

Transform OpenAPI specs into MCP tools instantly—no rewrites, no sidecar servers.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the Petstore MCP Server MCP server?

The Petstore MCP Server is a demonstration of HAPI MCP, a framework that automatically converts OpenAPI/Swagger specifications into Model Context Protocol tools. It exposes the Swagger Petstore API (v1.0.27) as MCP-compatible tools, enabling AI agents to interact with REST APIs without custom integration code.

HAPI MCP bridges OpenAPI specifications and MCP clients by automatically lifting API specs into agent-ready tools. The Petstore server demonstrates this capability using the standard Swagger Petstore API. It eliminates the need to rewrite business logic, keeps governance (auth, rate limits, permissions) inherited from your API layer, and works with any MCP client including Claude, ChatGPT, and QBot.

How to install Petstore MCP Server

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "petstore": {
      "url": "https://petstore.run.mcp.com.ai/mcp"
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • OpenAPI-to-MCP transformation — Automatically converts OpenAPI 3.0+ specifications into MCP tools with no manual rewrites
  • API tool exposure — Exposes REST API endpoints as callable MCP tools for AI agents
  • Auth and permission inheritance — Preserves API-layer authentication, RBAC, rate limits, and audit logs in MCP tools

Use cases

  • Test and prototype AI agent interactions with REST APIs using the Petstore example
  • Rapidly convert existing OpenAPI specs into MCP tools for integration with Claude, ChatGPT, or other MCP clients
  • Demonstrate API-first architecture where a single OpenAPI spec powers both traditional clients and AI agents
  • Build multi-tool orchestrated workflows using OrcA without rewriting API business logic
  • Enable internal support and ops teams to interact with APIs through conversational MCP clients

Petstore MCP Server MCP server FAQ

What is the Petstore MCP Server?

It's a live demonstration of HAPI MCP using the Swagger Petstore API (v1.0.27). It shows how any OpenAPI spec can be instantly transformed into MCP tools without code changes.

Do I need to rewrite my API to use this?

No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

Which AI clients can use these tools?

Any MCP client: Claude, ChatGPT, QBot, chatMCP, and custom orchestrators. The tools are vendor-neutral by design.

How do I install this in Cursor or Claude?

Connect via the remote streamable-HTTP endpoint: https://petstore.run.mcp.com.ai/mcp. Or install the HAPI CLI locally, point it to your OpenAPI spec, and run 'hapi serve path/to/swagger.json --headless'.

Is HAPI MCP free?

HAPI MCP is open-source under the MIT License. The CLI is free to use. runMCP offers serverless-like execution with pay-as-you-go pricing.

What security and compliance features are included?

Scoped credentials, per-tool permissions, rate limits, and audit logs are inherited directly from your API layer. No shadow logic or duplicate governance.

README (reference)

Source of truth, from the repository.

HAPI MCP – Headless API for Model Context Protocol

Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.

HAPI 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.

Key Features

  • No rewrites: Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.
  • Faster time-to-value: Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.
  • Reduced risk: Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.
  • Scales with you: runMCP delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.
  • Deterministic orchestration: OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.
  • Vendor-neutral: Works with any MCP client: ChatGPT, Claude, QBot, chatMCP. OAS + MCP + Arazzo stay portable.

How It Works

  1. Pick your API spec

    • OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.
    • Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.
  2. Run a single command

    • One simple CLI command transforms your API into a usable MCP Server.
    • No complex setup, zero configuration, works anywhere, cross-platform.
  3. Use instantly

    • Your API is now ready as a tool, AI agent, or testing interface.
    • MCP server ready, AI agent compatible, testing interface, developer experience friendly.

Visual Pipeline

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients
[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]
       (Your API)         →   (Transform)   →   (Usable Tool)
                                                 ↑          ↑
                                                 |          |
                                          [ ChatGPT ]  [ runMCP ]
                                          [ Claude  ]  [ OrcA   ]
                                          [ QBot    ]  [ chatMCP]
                                          [ Agents  ]

Who Wins With HAPI

  • Executives: Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.
  • Architects & PMs: Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.
  • Engineers & Ops: Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.

Your Stack, Already Wired

  • HAPI Server: Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.
  • runMCP: Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.
  • QBot: CLI TUI for power users to interact with MCP tools directly from terminal or scripts.
  • chatMCP: Conversational client that speaks MCP natively for support, ops, and internal assistants.
  • OrcA: Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.
  • Agents: Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.

Demos

Documentation

FAQ

  • Do we need to rewrite our services?
    No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

  • Is this just another MCP server?
    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.

  • Which clients can consume the tools?
    Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.

  • How do we keep control and compliance?
    Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.

  • What about security and privacy?
    Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.

  • How fast can we get started?
    You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.

Get Started

  1. Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases

  2. Transform your OpenAPI spec into an MCP server with a single command:

    hapi serve path/to/your/swagger.json --headless
    
  3. Start using your MCP tools with any compatible client!

  4. Explore the documentation for advanced usage and best practices.

Contributing

Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp

License

HAPI MCP is licensed under the MIT License. See LICENSE for details.

Related MCP servers

Official MCP Registry: publish and discover MCP servers like an app store for AI agents.

7.3k
Go
View repository →

Search and discover Agent Skills — reusable AI agent capability packages — from the skills.sh registry.

21k
Python
Apache-2.0
View repository →

Turn Strava APIs into AI-ready MCP tools instantly with HAPI—no rewrites, just OpenAPI specs.

9
HTML
MIT
View repository →

Turn Contabo's VPS API into AI-ready MCP tools instantly—no rewrites, full API control.

9
HTML
MIT
View repository →

One inbox for SMS and email: read threads, search, manage contacts, and send texts and emails.

COCompeller logo

Compeller

Maintained

Create and track AI music videos and audio-reactive visuals from songs.

1
MIT
View repository →