About Openapi MCP Proxy
Openapi MCP Proxy is an MCP server published by nyudenkov in the Developer Tools category: an MCP server that provides tools for exploring large OpenAPI schemas. It has been installed 0 times through Conduid.
The repository has 13 stars and 5 forks, with the last commit 11 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx openapi-mcp-proxyThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Openapi MCP Proxy
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
OpenAPI MCP Server
An MCP server that provides tools for exploring large OpenAPI schemas without loading entire schemas into LLM context. Perfect for discovering and analyzing endpoints, data models, and API structure efficiently.
Features
- API Configuration Management: Save and manage multiple API configurations with authentication headers if needed
- Schema Caching: Automatic caching of OpenAPI schemas to avoid repeated downloads
- Endpoint Discovery: List and search through API endpoints
- Pagination Support: Handle large APIs efficiently with configurable page sizes
- Detailed Schema Exploration: Get comprehensive information about endpoints and data models
- Efficient Context Usage: Explore large APIs without overwhelming LLM context windows

Prerequisites
- Python 3.13+: The server requires Python 3.13 or later
- uv: Fast Python package installer and resolver (installation guide)
- MCP-compatible client: Claude Desktop, Claude Code CLI, Cursor, or other MCP clients
Installing uv
macOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh
Using pip:
pip install uv
Installation
- Clone the repository:
git clone https://github.com/nyudenkov/openapi-mcp-proxy.git
cd openapi-mcp-proxy
- Install dependencies:
uv sync
- Verify installation:
# Test that the server starts correctly
uv run python main.py
The server should start without errors.
Usage
Running the Server
uv run python main.py
The server runs using stdio and integrates with MCP-compatible LLM clients.
Available Tools
API Management
-
add_api: Add a new API configuration with name, URL and optional descriptionname(required): Short name for the APIurl(required): URL to the OpenAPI scheme (yaml/json)description(optional): Optional descriptionheaders(optional): Optional HTTP headers for authentication (e.g., {'Authorization': 'Bearer token', 'X-API-Key': 'key'})
-
list_saved_apis: List all saved API configurations -
remove_api: Remove a saved API configuration
API Exploration
-
get_api_info: Get general information about an API -
list_endpoints: List all endpoints in an API with pagination and filtering -
search_endpoints: Search endpoints by query with pagination and filtering -
get_endpoint_details: Get detailed information about a specific endpoint -
list_models: List all data models in an API with pagination and filtering -
get_model_schema: Get detailed schema for a specific model
Tools Capabilities
Pagination
All listing tools (list_endpoints, search_endpoints, list_models) support pagination to handle large APIs efficiently:
- Default page size: 50 items
- Responses include navigation information (current page, total pages, has next/previous)
Advanced Filtering
Tools are capable to filter results to find exactly what you need:
Endpoint Filtering:
- HTTP methods (GET, POST, PUT, DELETE, etc.)
- Tags (include/exclude specific tags)
- Authentication requirements
- Deprecation status
Model Filtering:
- Model types (object, array, string, etc.)
- Property count (min/max number of properties)
- Required fields presence
- Tags (include/exclude specific tags)
Configuration
API configurations are automatically saved to api_configs.json in the working directory. The file structure:
{
"apis": {
"api-name": {
"name": "some-project-local-backend",
"url": "http://127.0.0.1:8000/openapi.json",
"description": "Optional description for some cool project local backend scheme"
},
"api-name": {
"name": "stripe-yaml",
"url": "https://raw.githubusercontent.com/stripe/openapi/refs/heads/master/openapi/spec3.yaml",
"description": "Stripe YAML OpenAPI scheme"
}
}
}
README mirrored from the source repository 3 months ago. The original is authoritative.
