npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kaisers-io/openapi-mcp

v0.2.0

Published

Turn any OpenAPI spec into a strict, locally running MCP server

Readme

openapi-mcp

Turn any OpenAPI spec into a strict, locally running MCP server.

openapi-mcp is a runtime wrapper — no code generation, no deployment. Point it at an OpenAPI 3.0/3.1 spec (URL or file) and every allowed operation becomes a validated MCP tool for hosts like Claude Code and Codex. It is read-only by default (only GET/HEAD operations, unless you pass --allow), reads secrets only from environment variables, and never applies a refreshed spec silently.

Trust the spec source. This tool interprets the OpenAPI document you give it at runtime, and that document's text flows into the model's context. A hostile spec is an injection surface — only point openapi-mcp at a spec source you trust.

Install

npm i -g @kaisers-io/openapi-mcp

Requirements: Node.js >=24.0, macOS or Linux.

Quick start

Claude Code (.mcp.json, expands ${VAR} — export SPEC_TOKEN/API_TOKEN first):

{
  "mcpServers": {
    "petstore": {
      "command": "npx",
      "args": [
        "-y",
        "@kaisers-io/[email protected]",
        "serve",
        "--spec",
        "https://api.example.com/openapi.json",
        "--spec-header-env",
        "Authorization=SPEC_TOKEN",
        "--header-env",
        "Authorization=API_TOKEN",
        "--allow",
        "read*",
        "--cache-key",
        "petstore"
      ],
      "env": { "SPEC_TOKEN": "${SPEC_TOKEN}", "API_TOKEN": "${API_TOKEN}" }
    }
  }
}

Codex CLI (config.toml, no ${VAR} expansion — export the secrets in your shell and whitelist them with env_vars):

[mcp_servers.petstore]
command = "npx"
args = [
  "-y", "@kaisers-io/[email protected]", "serve",
  "--spec", "https://api.example.com/openapi.json",
  "--spec-header-env", "Authorization=SPEC_TOKEN",
  "--header-env", "Authorization=API_TOKEN",
  "--allow", "read*",
  "--cache-key", "petstore",
]
env_vars = ["SPEC_TOKEN", "API_TOKEN"]

Host config examples always pin an exact version, never latest — this process runs with your API credentials on every launch.

Full documentation, security model, and configuration reference: https://github.com/kaisers-io/openapi-mcp

License

MIT