Openapi Inspector

Created By
Nonetss4 months ago
Stop pasting API docs. Let your LLM dynamically navigate OpenAPI/Swagger specs and extract precise JSON schemas on-demand.
Overview

What is OpenAPI Inspector?

OpenAPI Inspector is a professional OpenAPI explorer designed for the Model Context Protocol (MCP), allowing Large Language Models (LLMs) to dynamically explore, understand, and interact with APIs that have OpenAPI/Swagger specifications.

How to use OpenAPI Inspector?

To use OpenAPI Inspector, you can run the server directly using npx with the command: npx @nonetss/none.api. Alternatively, you can install it globally using npm with the command: npm install -g @nonetss/none.api.

Key features of OpenAPI Inspector?

  • Endpoint Listing: Provides an overview of all available routes.
  • Tag Discovery: Lists functional sections of the API.
  • Granular Schemas: Fetches specific JSON Schemas for precise code generation.
  • Dynamic URLs: Allows pointing to different OpenAPI specs on the fly.

Use cases of OpenAPI Inspector?

  1. Enabling LLMs to interact with various APIs without manual documentation.
  2. Assisting developers in understanding API structures quickly.
  3. Facilitating the generation of precise code based on API specifications.

FAQ from OpenAPI Inspector?

  • Can OpenAPI Inspector work with any API?

Yes! It works with any API that has an OpenAPI/Swagger specification.

  • Is OpenAPI Inspector free to use?

Yes! OpenAPI Inspector is free to use for everyone.

  • How does OpenAPI Inspector improve API interaction?

It allows LLMs to dynamically explore APIs, reducing the need for manual documentation and enhancing understanding.

Server Config

{
  "mcpServers": {
    "none.api": {
      "command": "npx",
      "args": [
        "-y",
        "@nonetss/none.api"
      ],
      "env": {
        "OPENAPI_URL": "http://localhost:3000/doc"
      }
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
Nonetss
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago