Openapi Navigator

Created By
mgaruccio9 months ago
MCP server for handling large openapi specs
Overview

What is OpenAPI Navigator?

OpenAPI Navigator is an MCP server designed to handle large OpenAPI specifications, making them easily accessible to AI agents without the need for manual JSON/YAML parsing.

How to use OpenAPI Navigator?

To use OpenAPI Navigator, load your OpenAPI spec from a local file or URL, and then utilize natural language queries to search for endpoints and schemas.

Key features of OpenAPI Navigator?

  • Load specs from local files or URLs (supports OpenAPI 3.x & Swagger 2.x)
  • Smart search with fuzzy matching for endpoints and schemas
  • Manage multiple API specifications simultaneously
  • Preserve reference structures for agent decision-making
  • Fast indexing for instant lookups and searches

Use cases of OpenAPI Navigator?

  1. API exploration to quickly understand API structure and capabilities.
  2. Code generation by extracting endpoint/schema information for automated code creation.
  3. Documentation generation for comprehensive API docs.
  4. Integration planning to discover API features before implementation.
  5. Testing by finding endpoints and parameters for test automation.

FAQ from OpenAPI Navigator?

  • Can OpenAPI Navigator handle all OpenAPI specs?

Yes! It supports both OpenAPI 3.x and Swagger 2.x specifications.

  • Is OpenAPI Navigator free to use?

Yes! OpenAPI Navigator is free to use for everyone.

  • How does OpenAPI Navigator improve API management?

It simplifies the process of navigating and managing large OpenAPI specs, allowing for efficient searches and integrations.

Server Config

{
  "mcpServers": {
    "openapi-navigator": {
      "command": "uvx",
      "args": [
        "openapi-navigator"
      ],
      "env": {}
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
mgaruccio
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)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago