Loading...
Transform OpenAPI 3.0 and 3.1 REST specifications into Model Context Protocol (MCP) server definitions, JSON Schemas, TypeScript `@modelcontextprotocol/sdk` servers, Python `mcp` servers, and Claude/Cursor configuration blocks. 100% client-side execution guarantees zero network transmission of proprietary API routes or internal schemas.
[
{
"name": "getCurrentWeather",
"description": "Get Current Weather",
"inputSchema": {
"type": "object",
"properties": {
"city": {
"type": "string",
"description": "City name or ZIP code (e.g., 'San Francisco, CA' or '94105')"
},
"units": {
"type": "string",
"description": "Temperature units ('celsius' or 'fahrenheit')",
"enum": [
"celsius",
"fahrenheit"
],
"default": "celsius"
}
},
"required": [
"city"
]
}
},
{
"name": "getWeatherForecast",
"description": "Get Weather Forecast",
"inputSchema": {
"type": "object",
"properties": {
"city": {
"type": "string",
"description": "Target location name"
},
"days": {
"type": "integer",
"description": "Number of forecast days (1 to 7)",
"default": 7
}
},
"required": [
"city"
]
}
}
]Get Current Weather
Get Weather Forecast
Paste any valid JSON OpenAPI 3.0 / 3.1 or Swagger specification into the editor, or choose from pre-loaded samples (Weather API, GitHub Repos, Petstore).
The local parser automatically transforms REST endpoints (`paths` and HTTP methods) into standard MCP tool declarations with parameter `inputSchema` mappings.
Copy or download production-ready `@modelcontextprotocol/sdk` TypeScript server code, Python `mcp` server scripts, or Claude Desktop `mcpServers` JSON.
Parse JSON and YAML Swagger / OpenAPI specifications directly inside browser memory without uploading sensitive internal API schemas to remote servers.
Convert REST endpoints (GET, POST, PUT, DELETE) into standard Model Context Protocol tool declarations with parameter inputSchema objects.
Instantly generate production-ready TypeScript (@modelcontextprotocol/sdk) and Python (mcp) server code boilerplates.
Export mcpServers configuration JSON files for Claude Desktop (`claude_desktop_config.json`), Cursor (`.cursor/mcp.json`), and Zed.
Explore real-world OpenAPI samples (Weather API, GitHub Repos, Petstore) or validate your custom API definitions with instant error feedback.
Our OpenAPI to MCP converter is open source under HiMat Technology. Inspect the parser logic, star the repository, or contribute on GitHub.
Unlike third-party API converters that require uploading your OpenAPI files to a remote backend, HiMat's tool executes 100% inside your local browser memory. Neither your internal microservice paths, payload schemas, nor authentication schemes ever leave your machine.
It is a free developer tool that converts RESTful OpenAPI 3.0 or 3.1 (Swagger) specifications into Model Context Protocol (MCP) server tool declarations, JSON Schemas, TypeScript/Python server code, and Claude/Cursor mcpServers configuration files.
Model Context Protocol (MCP) provides a unified standard for AI assistants like Claude Desktop, Cursor, and Zed to invoke external capabilities. By converting OpenAPI specs into MCP tools, AI agents can automatically inspect parameters and execute REST API calls.
No. All parsing, transformation, schema extraction, and code generation run 100% locally in your web browser. Your API endpoints, path parameters, and authentication schemes never leave your machine.
Yes! The converter supports both JSON and YAML OpenAPI 3.0 and 3.1 definitions, automatically detecting the format and validating the schema structure.
HiMat Technology builds custom AI agent architectures, multiagent orchestration pipelines, Model Context Protocol servers, and 21-day fixed-scope AI pilots with complete code ownership transfer.
Continue with related utilities, services, and guides from HiMat.