MCP OpenAPI Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| refresh-api-catalogC | Refresh the API catalog |
| get-api-catalogB | Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas |
| search-api-operationsC | Search for operations across specifications |
| search-api-schemasC | Search for schemas across specifications |
| load-api-operation-by-operationIdD | Load an operation by operationId |
| load-api-operation-by-path-and-methodC | Load an operation by path and method |
| load-api-schema-by-schemaNameC | Load a schema by schemaName |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, get-api-catalog retrieves metadata, load-api-operation-by-operationId and load-api-operation-by-path-and-method load operations via different identifiers, load-api-schema-by-schemaName loads schemas, refresh-api-catalog updates the catalog, and search-api-operations and search-api-schemas perform distinct searches. The descriptions clarify each tool's unique function, preventing misselection.
All tool names follow a consistent verb_noun pattern with hyphens, such as get-api-catalog, load-api-operation-by-operationId, and search-api-schemas. This predictability makes the set easy to navigate and understand, with no deviations in naming style across the seven tools.
With 7 tools, the server is well-scoped for managing OpenAPI specifications. Each tool earns its place by covering essential operations like retrieving, loading, refreshing, and searching metadata, schemas, and operations, without being overly sparse or bloated for the domain.
The tool surface is nearly complete for interacting with OpenAPI specifications, covering catalog retrieval, operation and schema loading, catalog refreshing, and searching. A minor gap exists in lacking direct update or delete operations for specifications, but agents can work around this by refreshing or reloading as needed, and core workflows are well-supported.