Skip to main content
Glama
roebi

transparent-openapi-mcp

by roebi

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.sh

2. 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.json

See 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.

A
license - permissive license
Not graded
quality - not tested
A
maintenance

Maintenance

Maintainers
Response time
Release cycle
1Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Converts 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.
    12
    5
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Transforms OpenAPI specs into an MCP server, enabling dynamic API interaction through natural language with automatic authentication and endpoint discovery.
    131
    MIT

View all related MCP servers

Related MCP Connectors

  • MCP server for AI access to Swagger by SmartBear.

  • Point Gecko at an OpenAPI spec; get first-call-correct, auth-hidden agent tools.

  • Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/roebi/transparent-openapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server