5 ms·
I just made a tool which parses any OpenAPI spec to MCP spec: https://www.open-mcp.org https://www.open-mcp.org (literally just deployed so I don't know if the
by dan-kwiat 1y ago
I just made a tool which parses any OpenAPI spec to MCP spec: https://www.open-mcp.org https://www.open-mcp.org (literally just deployed so I don't know if the DNS has propagated globally yet..)
- zomglings 1y agoI received a 500 response when I attempted to create an MCP server for an API. I was using this URL: https://engineapi.moonstream.to/metatx/openapi.json https://engineapi.moonstream.to/metatx/openapi.json The response body: {success: false, error: "Server URL must start with https:// or http://"}
- dan-kwiat 1y agoThanks, I just added support for relative URLs, try again. Your OpenAPI spec defines a relative base URL for the server /metatx but no domain. You can now specify the full base URL in your MCP client's environment variables: `OPEN_MCP_BASE_URL="https://engineapi.moonstream.to/metatx https://engineapi.moonstream.to/metatx"`
- orliesaurus 1y agovery cool, I tried to feed it the toolhouse.ai openapi spec and it worked VERY quickly!! wow