About Openapi Slice MCP
Openapi Slice MCP is an MCP server published by vvarp in the Developer Tools category: mCP server that extracts relevant portions of OpenAPI specs for specific endpoints, reducing context size when working with large API specifications.
The repository has 2 stars and 1 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/vvarp/openapi-slice-mcpThis 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 Slice MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 7 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
OpenAPI Slice MCP Server
An MCP (Model Context Protocol) server that helps you work with large OpenAPI specifications by extracting only the relevant portions for specific endpoints. This is particularly useful when working with LLMs that have context limitations - instead of loading an entire large OpenAPI spec, you can extract just the parts you need for a specific endpoint.
Features
- Endpoint-specific extraction: Get minimal OpenAPI specs containing only the requested endpoint and its dependencies
- Automatic dependency resolution: Recursively finds and includes all referenced components (schemas, parameters, etc.)
- Multiple formats: Output in YAML or JSON format
- File support: Load OpenAPI specs from local YAML or JSON files
- Remote support: Fetch OpenAPI specs directly from URLs (HTTP/HTTPS)
- Discovery tools: List all available endpoints in a loaded specification
Tools
The server provides the following MCP tools:
load_openapi_spec(file_path: str)- Load an OpenAPI specification from a local YAML or JSON fileload_openapi_spec_from_url(url: str, timeout: int = 30)- Load an OpenAPI specification from a remote URLlist_endpoints()- List all available endpoints in the currently loaded specificationextract_endpoint_slice(path: str, method: str, output_format: str = "yaml")- Extract a minimal spec slice for a specific endpointget_server_status()- Get the current status of the server
Usage
Running the Server
Stdio Mode (Default)
For local development and Claude Desktop integration:
uvx openapi-slice-mcp
The server runs using the STDIO transport and can be integrated with any MCP client.
HTTP Mode
For Smithery deployment or remote access:
# Using the dedicated HTTP entry point (runs on port 8000 by default)
uvx openapi-slice-mcp-http
# Or using the main entry point with --transport flag
uvx openapi-slice-mcp --transport http --host 0.0.0.0 --port 8000
The HTTP server exposes the MCP protocol at http://host:port/mcp.
README fetched from the repository 7 days ago. The original is authoritative.