petstormcp-cliente

Model Context Protocol (MCP) Server for the petstormcp-cliente API.

[!IMPORTANT] This MCP Server is not yet ready for production use. To complete setup please follow the steps outlined in your workspace. Delete this notice before publishing to a package manager.

Summary

Petstore - OpenAPI 3.1: This is a sample Pet Store Server based on the OpenAPI 3.1 specification.

Some useful links:

• OpenAPI Reference
• The Pet Store repository
• The source API definition for the Pet Store

For more information about the API: Find out more about Swagger

Table of Contents

• petstormcp-cliente
  • Installation
  • Progressive Discovery
  • Development
  • Publishing to Anthropic MCP Registry
  • Contributions

Installation

[!TIP] To finish publishing your MCP Server to npm and others you must run your first generation action.

{
  "command": "npx",
  "args": [
    "petstormcp-cliente",
    "start",
    "--environment",
    "prod",
    "--api-key",
    ""
  ]
}

claude mcp add Petstore -- npx -y petstormcp-cliente start --environment prod --api-key 

gemini mcp add Petstore -- npx -y petstormcp-cliente start --environment prod --api-key 

{
  "command": "npx",
  "args": [
    "petstormcp-cliente",
    "start",
    "--environment",
    "prod",
    "--api-key",
    ""
  ]
}

{
  "command": "npx",
  "args": [
    "petstormcp-cliente",
    "start",
    "--environment",
    "prod",
    "--api-key",
    ""
  ]
}

npx petstormcp-cliente start --environment prod --api-key 

npx petstormcp-cliente --help

Progressive Discovery

MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.

To enable dynamic mode, pass the --mode dynamic flag when starting your server:

{
  "mcpServers": {
    "Petstore": {
      "command": "npx",
      "args": ["petstormcp-cliente", "start", "--mode", "dynamic"],
      // ... other server arguments
    }
  }
}

In dynamic mode, the server registers only the following meta-tools instead of every individual tool:

• list_tools: Lists all available tools with their names and descriptions.
• describe_tool: Returns the input schema for one or more tools by name.
• execute_tool: Executes a tool by name with the provided input parameters.

This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.

Development

Run locally without a published npm package:

1. Clone this repository
2. Run npm install
3. Run npm run build
4. Run node ./bin/mcp-server.js start --environment prod --api-key To use this local version with Cursor, Claude or other MCP Clients, you'll need to add the following config:

{
  "command": "node",
  "args": [
    "./bin/mcp-server.js",
    "start",
    "--environment",
    "prod",
    "--api-key",
    ""
  ]
}

Or to debug the MCP server locally, use the official MCP Inspector:

npx @modelcontextprotocol/inspector node ./bin/mcp-server.js start --environment prod --api-key 

Publishing to Anthropic MCP Registry

This server generates a server.json that conforms to the official MCP Registry schema. You can publish automatically via your Speakeasy workflow or manually using the mcp-publisher CLI.

Automated Publishing (Recommended)

Add mcpRegistry to the publish block in your workflow.yaml:

targets:
  my-mcp:
    target: mcp-typescript
    source: my-source
    publish:
      npm:
        token: $NPM_TOKEN
      mcpRegistry:
        auth: github-oidc  # recommended, no token needed

The github-oidc method uses GitHub Actions OIDC — no secrets required. For other auth methods:

• github — requires a MCP_REGISTRY_TOKEN secret (GitHub PAT with read:org + read:user scopes)
• dns — requires a MCP_REGISTRY_TOKEN secret (Ed25519 private key for custom domain namespaces)

When the Speakeasy workflow runs, it will automatically publish to npm first, then to the MCP Registry.

Manual Publishing

If you prefer to publish manually, follow the official publishing guide:

1. Publish to npm: npm publish --access public
2. Install the publisher CLI:

   curl -sL "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher && sudo mv mcp-publisher /usr/local/bin/
   

3. Authenticate (GitHub OAuth for io.github.* namespaces):

   mcp-publisher login github
   

4. Publish: mcp-publisher publish
5. Verify:

   curl "https://registry.modelcontextprotocol.io/v0/servers?search=<your-mcp-name>"
   

Contributions

While we value contributions to this MCP Server, the code is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

MCP Server Created by Speakeasy