{"uid":"cap_wlxqsiYKKuaVWM7RZ1deN","slug":"openapi-to-mcp-tool-converter-7b6fac71","name":"OpenAPI to MCP Tool Converter","description":"Converts each OpenAPI operation into an MCP tool. Path, query and header parameters and the JSON request body are merged into one input schema, because MCP tools take exactly one; a name collision between a body field and a parameter is reported rather than silently overwritten. Internal $refs are expanded inline so each tool schema stands alone — an MCP client cannot resolve them.","url":"https://modell.halowerk.com/v1/openapi-to-mcp","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"naming":{"enum":["snake_case","preserve"],"type":"string","default":"snake_case","description":"How to normalise tool names."},"prefix":{"type":"string","maxLength":40,"description":"Prefix for every tool name, to keep several APIs apart in one client."},"document":{"type":"object","description":"The OpenAPI 3.x document as JSON."},"include_methods":{"type":"array","items":{"type":"string"},"description":"Only convert these HTTP methods, e.g. [\"get\"] for a read-only server."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_snq4Kg23qulnLw6FjUuTv","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Converts an OpenAPI 3.x document into a set of MCP tool definitions, merging path/query/header parameters and request body into a single flat input schema per operation with inline-expanded $refs.","exampleAgentPrompt":"Convert my OpenAPI 3 spec into MCP tool definitions — here's the full spec JSON — and make sure all $refs are expanded inline and any parameter/body name collisions are flagged.","exampleUseCases":[{"title":"Expose REST API to AI agents","prompt":"I have an OpenAPI 3 spec for my payments API and I want to make it available as MCP tools so my AI agent can call it — can you convert the spec into MCP tool definitions with all parameters merged into one input schema?"},{"title":"Inline $refs for standalone tool schemas","prompt":"My OpenAPI spec uses a lot of $ref references throughout the schemas — convert it to MCP tools and expand all those $refs inline so each tool schema is completely self-contained and doesn't need external resolution."},{"title":"Detect parameter and body name collisions","prompt":"Before I ship my OpenAPI-to-MCP integration, can you run my spec through the converter and tell me if any of my path, query, or header parameter names clash with fields in the request body?"}],"resultDescription":"A set of MCP tool definitions — one per OpenAPI operation — where each tool has a single flat input schema combining all path, query, header parameters and the JSON request body fields. All internal $refs are expanded inline so each schema is self-contained. Any name collisions between body fields and parameters are reported as errors rather than silently overwritten.","failureModes":["Invalid or malformed OpenAPI 3.x document causes parsing failure","Unsupported OpenAPI version (e.g. Swagger 2.x) returns an error","Circular $ref references may cause expansion failures or infinite loops","Name collisions between body fields and parameters are reported as errors and may block conversion","Missing required openapi/info/paths fields cause validation errors","Extremely large specs may time out or exceed payload limits"],"whenToPreferThis":"Use this endpoint when you need to expose an existing OpenAPI 3.x API to MCP clients or AI agents and want each operation represented as a standalone MCP tool with a single, flat, fully self-contained input schema. It is the right choice when your spec uses $refs that MCP clients cannot resolve, or when you need explicit collision detection between parameter names and body fields rather than silent overwrites.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T00:31:41.637Z","isFirstParty":false}