Openapi Inspector
@Nonetss
About Openapi Inspector
Stop pasting API docs. Let your LLM dynamically navigate OpenAPI/Swagger specs and extract precise JSON schemas on-demand.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"none.api": {
"command": "npx",
"args": [
"-y",
"@nonetss/none.api"
],
"env": {
"OPENAPI_URL": "http://localhost:3000/doc"
}
}
}
}Tools
17STEP 1 (EXPLORATION): List all available endpoints. ALWAYS use this first to understand the API capabilities and available routes before developing any feature.
STEP 2 (ANALYSIS): Get full technical details of a specific endpoint, including required parameters, headers, and response structure. Use this before writing any code.
FRONTEND (TYPING): Generate TypeScript interfaces for request bodies and response data. Essential for maintaining type safety in frontend development.
FRONTEND (VALIDATION): Generate Zod validation schemas for request or response bodies. Perfect for implementing form validation that matches backend rules.
FRONTEND (IMPLEMENTATION): Generate complete code snippets for modern frameworks like Axios or TanStack Query, including error handling and types.
BACKEND (TESTING): Validate a JSON object against the OpenAPI response schema. ALWAYS use this after writing backend code to verify your implementation matches the contract.
FRONTEND (PROTOTYPING): Generate high-fidelity mock data that satisfies the OpenAPI schema. Use this to test UI components before the backend is fully ready.
SEARCH: Find endpoints by intent or keyword (e.g., 'delete user', 'upload file'). Useful when you know what you want to do but not the exact route.
ARCHITECTURE: Analyze ID relationships between endpoints. Use this to understand the data flow and which endpoint provides the ID required by another.
Search for endpoints by tag.
Get the JSON request body schema for an endpoint.
Get the JSON response body schema for an endpoint.
List all tags available in the OpenAPI specification.
Generate a fetch code snippet for an endpoint.
Get security requirements for the API or a specific endpoint.
Set authentication headers to be used for subsequent 'call_endpoint' requests.
DEBUG: Execute a real HTTP request to the configured API to verify live behavior and connectivity.
Overview
What is Openapi Inspector?
Openapi Inspector is a professional OpenAPI explorer server for the Model Context Protocol (MCP). It allows large language models like Claude or Cursor to dynamically explore, understand, and interact with any API that has an OpenAPI/Swagger specification.
How to use Openapi Inspector?
Run the server directly with npx @nonetss/none.api (or install globally with npm install -g @nonetss/none.api). Configure it in your MCP client (e.g., claude_desktop_config.json) with the command npx -y @nonetss/none.api and set the OPENAPI_URL environment variable to point to your OpenAPI spec.
Key features of Openapi Inspector
- List all available endpoints and methods
- Discover functional sections via tag search
- Fetch granular JSON Schemas for requests and responses
- Support for dynamic OpenAPI URLs at runtime
- Optimized for backends following the hono-template structure
Use cases of Openapi Inspector
- Allow an LLM to understand an unfamiliar API without pasting documentation manually
- Enable code generation by retrieving precise request/response schemas
- Reduce context overload by inspecting endpoints on demand instead of mapping all to tools
- Browse and search API operations interactively during conversation
FAQ from Openapi Inspector
How does Openapi Inspector differ from other MCP API servers?
Instead of mapping every endpoint to a separate tool (which can overwhelm the model's context), it acts as an intelligent inspector that lists endpoints, searches by tags, and retrieves detailed information and schemas on demand.
What are the runtime requirements?
Node.js and npm/npx. The server runs as a command-line MCP server and requires an MCP‑compatible client (e.g., Claude Desktop, Cursor).
Where does the API data come from?
It fetches the OpenAPI specification from the URL provided in the OPENAPI_URL environment variable. The URL can be changed dynamically.
Is authentication supported?
The README does not describe any built‑in authentication mechanism. Authentication must be handled by the OpenAPI endpoint or the client configuration separately.
Are there any known limitations?
The server is optimized for backends following the hono-template structure but works with any valid OpenAPI/Swagger specification. No other limitations are mentioned in the README.
Frequently asked questions
How does Openapi Inspector differ from other MCP API servers?
Instead of mapping every endpoint to a separate tool (which can overwhelm the model's context), it acts as an intelligent inspector that lists endpoints, searches by tags, and retrieves detailed information and schemas on demand.
What are the runtime requirements?
Node.js and npm/npx. The server runs as a command-line MCP server and requires an MCP‑compatible client (e.g., Claude Desktop, Cursor).
Where does the API data come from?
It fetches the OpenAPI specification from the URL provided in the `OPENAPI_URL` environment variable. The URL can be changed dynamically.
Is authentication supported?
The README does not describe any built‑in authentication mechanism. Authentication must be handled by the OpenAPI endpoint or the client configuration separately.
Are there any known limitations?
The server is optimized for backends following the hono-template structure but works with any valid OpenAPI/Swagger specification. No other limitations are mentioned in the README.
Basic information
More Developer Tools MCP servers
OrangePro
Aamir SiddiquiOrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.
SecondSim
econdSim provisions real UK mobile numbers (non-VoIP) via eSIM, built for freelancers, sole traders, small businesses, and enterprise teams. Unlike VoIP apps and virtual numbers, SecondSim numbers register as genuine phy
TaskerArmy Agent
TaskerArmyAsk Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.
endoflife.ai
endoflife.aiFree MCP server for software end-of-life intelligence: EOL dates, support status, and the 0-100 EOL Risk Score across 480+ tracked products. Agents can check a single version, pull a product's full lifecycle schedule, or
Agent Conductor
icohangar-opsAgent conductor — AGENTS.md contract parser, SKILL.md registry, CHP decision engine over MCP
Comments