load_apiLABSCO SUMMARY
The spec stays out of the context window until the model asks.
A large OpenAPI file pasted into a conversation eats the budget and still gets misread. Here it is loaded once under an ID and the model pulls one endpoint at a time, asking for prose rather than schema when that is easier to reason over. Several APIs can be loaded side by side, which is how you get a model to work across two services.
What it is
A Node server that holds one or more OpenAPI or Swagger specifications in memory under IDs you choose, and answers questions about them one endpoint at a time.
What you get
- load_api to bring a spec in from a URL or a file path under an apiId of your choosing
- list_apis for everything currently loaded
- search_endpoints to find endpoints matching a pattern in the path or the description
- get_endpoint_details for one method and path, with a natural flag that returns a human-readable summary instead of raw schema
- The same material as resources: an overview per API, its endpoint list, and a single endpoint by method and path
Requirements
Node, and a clone of the repository built with npm; the built index.js is referenced by absolute path in the client config. Specifications are loaded at runtime by load_api, so nothing is fixed in advance.
Setup effort
Build from source — git clone https://github.com/gulbaki/swagger-mcp-server
USE CASES
01
Writing a client against an API you have never used
Load the spec, search for the endpoints that matter, and read their details as a summary rather than as raw schema.
02
Answering what a specific call expects
Fetch the one method and path in question instead of scrolling the whole document.
03
Finding every endpoint that touches one concept
Search the loaded spec by pattern across paths and descriptions.
04
Working across two services at once
Load each spec under its own ID, then check what is loaded before asking a cross-API question.
4 tools
Listed in project docs. Your client may show a different list.
get_endpoint_detailslist_apissearch_endpointsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/gulbaki/swagger-mcp-server
cd swagger-mcp-server
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"swagger-explorer": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SWAGGER_MCP_SERVER>/build/index.js"
]
}
}
}
