specbridge_list_specsLABSCO SUMMARY
Any API with an OpenAPI spec becomes callable without writing a server for it.
Download a spec into the folder, restart the server, and its operations are tools. Specs are read and written whole, which suits documents that are regenerated as often as they are hand-edited. A spec with POST operations produces tools that write, so the specs you drop in decide what the agent can change.
What it is
A server that turns the OpenAPI spec files in a folder into MCP tools, one per operation, plus four tools for managing the spec files themselves.
What you get
- The specification files in the folder listed, one read, one written, and one downloaded from a URL straight into the folder under a filename you choose.
- One tool per operation in every spec in the folder, named from the spec's filename and operationId — petstore.json's getPetById becomes petstore_getPetById
- Credentials per API read from environment variables named after the spec file — PETSTORE_API_KEY, GITHUB_TOKEN — as an API key, bearer token or basic auth
Requirements
A specs folder on disk for the specification files to live in.
Setup effort
One command — npm install -g specbridge
USE CASES
01
Calling an API that has no MCP server of its own
Put its OpenAPI spec in the folder and each operation becomes a tool, with the key read from an environment variable named after the spec file.
02
Bringing a spec into the local folder to work against
The download writes it into the specs folder under a filename you choose, which is where the other tools look for it.
03
Correcting a specification that does not match reality
The file is read whole and written whole, so an edit is a deliberate replacement rather than an accumulation of patches.
4 tools
Listed in project docs. Your client may show a different list.
specbridge_get_specspecbridge_download_specspecbridge_update_specBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation. Beyond specbridge_list_specs, specbridge_get_spec, specbridge_download_spec and specbridge_update_spec, every OpenAPI file in the --specs folder adds {api_name}_{operationId} tools, and a spec with POST operations produces tools that write.
Requires
npx on PATH
Where it runs
All 4 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g specbridgeMCP Clients
Claude Desktop — global npm, Cursor — global npm
JSON
{
"mcpServers": {
"specbridge": {
"command": "specbridge",
"args": [
"--specs",
"<YOUR_PATH_TO_SPECS_FOLDER>"
]
}
}
}Claude Desktop — npx, Cursor — npx
JSON
{
"mcpServers": {
"specbridge": {
"command": "npx",
"args": [
"-y",
"specbridge",
"--specs",
"<YOUR_PATH_TO_SPECS>"
]
}
}
}
