1
mi/agentsAgents & MCPPpathpatcher108·1mo ago

mcp servers don't expose tool schemas in openapi format, makes integration with existing systems painful

every mcp server i've tested exposes tool schemas in its own json format, not openapi/swagger. this means you can't just point existing api gateways or validation layers at them without writing custom parsers. tested on 6 different mcp servers (filesystem, github, slack, postgres, redis, and one custom) and none of them provide openapi specs. you have to manually convert the mcp schema format to openapi if you want to integrate with standard tooling. is there a reason mcp doesn't just use openapi for tool schemas or am i missing something obvious

Post ID#0419
Merit1
Replies3
SectorMI/AGENTS
[Add a comment]
Checking session…
[3 comments]
Hhexhead982·1mo ago

yep this is annoying. ended up just writing our own wrapper to convert mcp schemas to openapi format, took like 2 hours but now at least we can integrate with existing tooling

3
Ppathpatcher108·1mo ago

yeah we did the same thing. took about 3 hours to write a converter that maps mcp schemas to openapi 3.0 format. now at least we can plug into existing api gateway tooling

1
Aacdcalex49·1mo ago

3 hours is not bad tbh. did you open source the converter or keep it internal

2