transparent-openapi-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
transparent-openapi-mcp
A KISS MCP server that maps OpenAPI v3 specifications 1:1 onto MCP tools, transparently - a change to a loaded OpenAPI spec never requires a change to this server's own code.
Using this as a Claude Code MCP server
Three steps: build the image, set up your server-side config, wire it into Claude Code.
1. Build
./podman_build.sh2. Configure the server
The server needs its own config: a local file (mounted into the
container) that points at a config list, which in turn points at your
OpenAPI spec(s) and backend(s). See
examples/README.md for the full reference -
what each file contains, the <prefix>_<operationId> tool naming
rule, and a runnable example set proven to work end-to-end.
3. Wire it into Claude Code
Claude Code needs to know how to start the container as a stdio
subprocess. See
examples/claude-code/README.md
for the exact MCP config entry to add and how it relates to your
server-side config from step 2.
Once added, run /mcp in a Claude Code session and confirm
transparent-openapi-mcp shows up with its tools.
Related MCP server: ControlAPI-MCP
Try it with the bundled example
Before wiring in your own real spec/backend, you can verify the whole chain works using the bundled minimal example:
./podman_build.sh
mkdir -p ~/t-o-m-config
cp examples/*.example.json ~/t-o-m-config/
cd ~/t-o-m-config
mv local-config.example.json local-config.json
mv config-list.example.json config-list.json
mv minimal-openapi.example.json minimal-openapi.json
# in another terminal, serve that directory:
cd ~/t-o-m-config && python3 -m http.server 8000
# back in the first terminal:
./podman_run.sh ~/t-o-m-config/local-config.jsonSee examples/README.md for
the full walkthrough, including how to actually call a tool and see
a result (this just starts the server - it sits silently on stdio,
which is correct MCP behavior).
Design docs
See docs/core-mcp-server/requirements.md and
docs/core-mcp-server/architecture.md for the full requirement set
(R-CTRL, R-DEPLOY, R-CFG, R-BOOT, R-TOOLS, R-FWD, R-STACK, R-RELEASE)
and design.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for AI access to Swagger by SmartBear.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceExposes OpenAPI specifications as MCP tools, enabling AI assistants to explore and understand API structures, endpoints, schemas, and documentation through semantic queries.19 npmMIT
- AlicenseAqualityDmaintenanceConverts any OpenAPI/REST API into MCP tools with dynamic server switching, variable substitution, and runtime configuration. Enables seamless interaction with multiple API environments through natural language without pre-configuration.125MIT
- AlicenseNot gradedqualityDmaintenanceTransforms OpenAPI specs into an MCP server, enabling dynamic API interaction through natural language with automatic authentication and endpoint discovery.131 npmMIT
- AlicenseNot gradedqualityDmaintenanceAuto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.17 npmMIT