SpecBridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | HTTP bind host for the MCP server when using HTTP transport. | |
| MCP_HTTP_PATH | No | MCP endpoint path, such as '/mcp', for HTTP transport. | |
| MCP_HTTP_PORT | No | HTTP port for the MCP server when using HTTP transport. | |
| MCP_TRANSPORT | No | Transport mode for the MCP server, either 'stdio' or 'http'. | stdio |
| OPENAPI_BACKENDS | No | JSON array of backend configurations. | |
| DEFAULT_BACKEND_ID | No | Default backend ID; if unset, uses 'swagger-petstore'. | swagger-petstore |
| MCP_HTTP_STATELESS | No | Set to 'true' for stateless HTTP mode. | |
| OPENAPI_CACHE_TTL_MS | No | In-memory spec cache TTL in milliseconds. | |
| OPENAPI_BACKENDS_FILE | No | Path to a backend config JSON file. | |
| OPENAPI_FETCH_TIMEOUT_MS | No | Fetch timeout for spec loading in milliseconds. | |
| OPENAPI_ENABLE_SWAGGER_UI_SCRIPT_EXTRACTION | No | Opt in to strict JSON object extraction from static Swagger UI scripts; fetched JavaScript is never executed. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_backendsB | List configured backend targets available for OpenAPI tools. |
| load_openapi_specA | Load or refresh OpenAPI spec from a URL. Use this first if tools fail because docs path changed. |
| list_api_endpointsC | List endpoints from the currently loaded OpenAPI document. |
| get_endpoint_contractA | Return full contract for one endpoint: params, request schema, response schema, and referenced DTO names. |
| generate_typescript_dtoB | Generate TypeScript DTO type declarations from OpenAPI components schema. Includes referenced nested DTO types. |
| propose_new_endpointB | Create a best-effort endpoint + DTO proposal aligned with deterministic patterns found in the current OpenAPI spec. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/heecheon92/specbridge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server