About Openapi Inspector
Openapi Inspector is an OpenAPI MCP server for frontend development and backend contract verification. It lets LLMs explore API specifications on demand, generate types and code snippets, and check response data against the contract.
Key features
- 01Browse and search categorized endpoints
- 02Retrieve request and response JSON schemas
- 03Generate TypeScript types and Zod schemas
- 04Generate data-fetching code and mock data
- 05Validate responses and map dependencies
- 06Inspect security requirements and call endpoints
Use cases
- 01Generate frontend types and validation schemas from an API spec
- 02Create mock data for UI prototypes
- 03Check backend responses against an API contract
- 04Explore endpoints and their data dependencies
MCP support
It exposes OpenAPI endpoint exploration, schema retrieval, code generation, and response validation tools to MCP clients; it can also configure authentication and call APIs.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
17Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | number | No | Limit the number of results (default: 50). |
| offset | number | No | Starting index for pagination (default: 0). |
Details
From the project READMEnone.api - OpenAPI Explorer MCP Server
Professional OpenAPI explorer for the Model Context Protocol (MCP), optimized for Frontend Development and Backend Contract Verification.
What is this?
This MCP server allows Large Language Models (LLMs) like Claude or Cursor to dynamically explore, understand, and interact with any API that has an OpenAPI/Swagger specification.
It is specifically designed to:
- Accelerate Frontend Development: Generate types, Zod schemas, mock data, and data-fetching hooks (Axios/TanStack Query) directly from the API definition.
- Verify Backend Implementation: Validate backend response objects against the OpenAPI contract to ensure the implementation matches the specification.
Installation
Using npx (Recommended)
You can run the server directly without installation:
npx @nonetss/none.api
Global Installation
npm install -g @nonetss/none.api
Key Features
- Smart Exploration: Categorized endpoint listing and keyword-based search (with multilingual synonym support).
- Frontend Factory:
- Generate TypeScript Interfaces for requests and responses.
- Generate Zod Schemas for form validation.
- Generate React/Axios/TanStack Query snippets.
- Generate Mock Data for UI prototyping.
- Backend Guard:
- Response Validation: Compare JSON data against OpenAPI schemas using
AJV. - Dependency Mapping: Understand relationships between resources (e.g., which endpoint provides the ID needed for another).
- Response Validation: Compare JSON data against OpenAPI schemas using
- Security: Automatic authentication support (Bearer/API Key) and secure environment-locked configuration.
Tools Overview
| Tool | Focus | Description |
|---|---|---|
list_endpoints | Exploration | Lists all endpoints grouped by functional categories. |
list_tags | Exploration | Lists all tags (functional categories) in the API. |
search_by_tag | Exploration | Lists all endpoints associated with a specific tag. |
find_endpoint | Exploration | Intelligent search by intent or keyword (e.g., "delete user"). |
get_endpoint_info | Analysis | Detailed documentation, parameters, and response codes. |
get_request_schema | Analysis | Returns the JSON schema for an endpoint's request body. |
get_response_schema | Analysis | Returns the JSON schema for a specific response status code. |
get_typescript_types | Frontend | Generates ready-to-use TypeScript interfaces. |
get_zod_schema | Frontend | Generates Zod validation schemas. |
get_framework_snippet | Frontend | Generates Axios or TanStack Query code. |
get_fetch_snippet | Frontend | Generates a native fetch snippet for quick integration. |
get_mock_data | Prototyping | Generates high-fidelity mock data based on schemas. |
map_dependencies | Architecture | Analyzes data flow and ID relationships between routes. |
get_security_info | Security | Shows security requirements for the API or specific routes. |
set_security_context | Security | Sets authentication headers for subsequent requests. |
call_endpoint | Debug | Executes real HTTP calls to the configured API. |
validate_response | Backend | Validates a JSON object against the API contract. |
Configuration
Add this to your claude_desktop_config.json or Cursor MCP settings:
{
"mcpServers": {
"none.api": {
"command": "npx",
"args": ["-y", "@nonetss/none.api"],
"env": {
"OPENAPI_URL": "http://localhost:3000/doc",
"AUTH_EMAIL": "[email protected]",
"AUTH_PASSWORD": "your-password",
"AUTH_PATH": "/api/auth/login"
}
}
}
}
Development Workflow
- Build:
npm run build(usestsc+tsc-aliasfor path resolution). - Formatting: Prettier is included.
- Git Hooks: Automated formatting on commit via
huskyandlint-staged.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.