A comprehensive Model Context Protocol (MCP) implementation for the Swagger Petstore API. This project includes both a complete MCP server and a
Mcpforrestapis mcp server connects Mcpforrestapis to AI assistants that speak the Model Context Protocol. A comprehensive Model Context Protocol (MCP) implementation for the Swagger Petstore API. This project includes both a complete MCP server and a sophisticated client system for seamless agent integration.
A comprehensive Model Context Protocol (MCP) implementation for the Swagger Petstore API. This project includes both a complete MCP server and a sophisticated client system for seamless agent integration.
This project provides: - MCP Server: Complete implementation of all Petstore API endpoints - MCP Client: High-level client with agent-friendly interfaces - Agent Integration: Ready-to-use components for AI agents - Configuration Management: Flexible configuration system - Prompt Templates: Pre-built prompts for different scenarios
Once connected, the assistant can call these 14 tools directly:
add_pet — Add a new pet to the storeupdate_pet — Update an existing petget_pet_by_id — Find pet by IDfind_pets_by_status — Find pets by status (available, pending, sold)find_pets_by_tags — Find pets by tagsupdate_pet_with_form — Update a pet using form datadelete_pet — Delete a petupload_pet_image — Upload an image for a petget_inventory — Get pet inventories by statusplace_order — Place an order for a petget_order_by_id — Find purchase order by IDdelete_order — Delete purchase order by IDcreate_user — Create a new usercreate_users_with_list — Create multiple users from a listSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Mcpforrestapis sits in that group, and the shape of its toolset — add_pet, update_pet, get_pet_by_id among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| add_pet | Add a new pet to the store |
| update_pet | Update an existing pet |
| get_pet_by_id | Find pet by ID |
| find_pets_by_status | Find pets by status (available, pending, sold) |
| find_pets_by_tags | Find pets by tags |
| update_pet_with_form | Update a pet using form data |
| delete_pet | Delete a pet |
| upload_pet_image | Upload an image for a pet |
| get_inventory | Get pet inventories by status |
| place_order | Place an order for a pet |
| get_order_by_id | Find purchase order by ID |
| delete_order | Delete purchase order by ID |
| create_user | Create a new user |
| create_users_with_list | Create multiple users from a list |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.