Petstore MCP Server

ai.com.mcpPublished by mcp.com.aiOfficial publisherv0.6.0Updated Oct 24, 2026

Swagger Petstore API (v1.0.27) as MCP for testing and prototyping powered by the HAPI MCP server

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint exposing the Swagger Petstore sample API, letting an assistant manage pets, orders, inventory and users for testing and prototyping.

What you can do
  • Create, update and delete pets, and look up pets by ID, status or tags
  • Upload an image file for a pet
  • Check inventory quantities by status
  • Place, look up and delete purchase orders
  • Create, log in, log out, read, update and delete store users
When to use it
Useful when you want to try MCP tool calling against a well-known sample API, demo an assistant's ability to call REST-style tools, or prototype agent workflows without building a backend.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The manifest declares no authentication, though some user tools state they can only be done by the logged-in user.
Before you install
Tools write and delete data: pets, orders and users can be created, changed or removed, and files can be uploaded. User tools include login and logout, and the manifest declares no authentication, so treat any data sent as non-private. It is a public demo store, not a production system.

Installation

In SourceWeft

  1. Open Petstore MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.com.mcp%2Fpetstore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "petstore": {
      "type": "http",
      "url": "https://petstore.run.mcp.com.ai/mcp"
    }
  }
}

README

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:

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

Source: README.md at commit 1873ff7

Tools

19

updatePet

Update an existing pet. - Update an existing pet by Id.

ParametersupdatePetBodyrequiredx-hapi-auth-state

addPet

Add a new pet to the store. - Add a new pet to the store.

ParametersaddPetBodyrequiredx-hapi-auth-state

findPetsByStatus

Finds Pets by status. - Multiple status values can be provided with comma separated strings.

Parametersstatusrequiredx-hapi-auth-state

findPetsByTags

Finds Pets by tags. - Multiple tags can be provided with comma separated strings. Use tag1, tag2, tag3 for testing.

Parameterstagsrequiredx-hapi-auth-state

getPetById

Find pet by ID. - Returns a single pet.

ParameterspetIdrequiredx-hapi-auth-state

updatePetWithForm

Updates a pet in the store with form data. - Updates a pet resource based on the form data.

ParametersnamepetIdrequiredstatusx-hapi-auth-state

deletePet

Deletes a pet. - Delete a pet.

ParameterspetIdrequiredapi_keyx-hapi-auth-state

uploadFile

Uploads an image. - Upload image of the pet.

ParameterspetIdrequireduploadFileBodyx-hapi-auth-stateadditionalMetadata

getInventory

Returns pet inventories by status. - Returns a map of status codes to quantities.

Parametersx-hapi-auth-state

placeOrder

Place an order for a pet. - Place a new order in the store.

ParametersplaceOrderBodyx-hapi-auth-state

getOrderById

Find purchase order by ID. - For valid response try integer IDs with value <= 5 or > 10. Other values will generate exceptions.

ParametersorderIdrequiredx-hapi-auth-state

deleteOrder

Delete purchase order by identifier. - For valid response try integer IDs with value < 1000. Anything above 1000 or non-integers will generate API errors.

ParametersorderIdrequiredx-hapi-auth-state

createUser

Create user. - This can only be done by the logged in user.

ParameterscreateUserBodyx-hapi-auth-state

createUsersWithListInput

Creates list of users with given input array. - Creates list of users with given input array.

Parametersx-hapi-auth-statecreateUsersWithListInputBody

loginUser

Logs user into the system. - Log into the system.

Parameterspasswordusernamex-hapi-auth-state

logoutUser

Logs out current logged in user session. - Log user out of the system.

Parametersx-hapi-auth-state

getUserByName

Get user by user name. - Get user detail based on username.

Parametersusernamerequiredx-hapi-auth-state

updateUser

Update user resource. - This can only be done by the logged in user.

ParametersusernamerequiredupdateUserBodyx-hapi-auth-state

deleteUser

Delete user resource. - This can only be done by the logged in user.

Parametersusernamerequiredx-hapi-auth-state

Version history

1
  1. v0.6.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts