Expose API endpoints as strongly typed tools from an OpenAPI specification. Supports OpenAPI 2.0/3.0 in JSON or YAML format, from local or remote files.
Operations ('endpoints') from your OpenAPI specification are translated to MCP tools. All path/query/JSON body parameters are exposed (using their JSON schema). Response is returned as-is. By default, the tool name is computed using first the operation.x-mcp-tool-name extension, then the operation.operationId and then {httpMethod}_{escaped_path}. The tool naming strategy can be defined via the --tool-naming-strategy option. Tools are discarded if their name don't match ^[a-zA-Z0-9_-]{1,64}$. Tools description are extracted as follows: operation.x-mcp-tool-description ?? operation.description ?? path.description.