OpenAPI to MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | API Key for the target API (if required) | |
| CONFIG_FILE | No | Path to a JSON configuration file | |
| DISABLE_X_MCP | No | Set to `true` to disable adding the `X-MCP: 1` header to all API requests | |
| CUSTOM_HEADERS | No | JSON string containing custom headers to include in all API requests | |
| OPENAPI_SPEC_PATH | No | Path to OpenAPI spec file | |
| TARGET_API_BASE_URL | No | Base URL for API calls (overrides OpenAPI servers) | |
| SECURITY_CREDENTIALS | No | JSON string containing security credentials for multiple schemes | |
| SECURITY_SCHEME_NAME | No | Name of the security scheme requiring the API Key | |
| OPENAPI_OVERLAY_PATHS | No | Comma-separated paths to overlay JSON files | |
| MCP_BLACKLIST_OPERATIONS | No | Comma-separated list of operation IDs or URL paths to exclude (supports glob patterns, ignored if whitelist used) | |
| MCP_WHITELIST_OPERATIONS | No | Comma-separated list of operation IDs or URL paths to include (supports glob patterns like `getPet*` or `GET:/pets/*`) |
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 |
|---|---|
| listPetsD | – |
| createPetD | – |
| getPetByIdD | – |
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 3 tools
The three tools have clearly distinct purposes: createPet for creating a pet, getPetById for retrieving a specific pet by ID, and listPets for listing all pets. There is no overlap or ambiguity between these operations, making it easy for an agent to select the correct tool based on the desired action.
All tool names follow a consistent verb_noun pattern: createPet, getPetById, and listPets. The naming is uniform, with no mixing of conventions (e.g., snake_case or camelCase variations), making the set predictable and readable.
With only 3 tools, the server feels thin for a general OpenAPI-to-MCP conversion purpose, which might imply broader functionality. However, for a specific pet-related API subset, this count is minimal but covers basic CRUD operations (create, read, list), though it lacks update and delete tools.
The tool set covers create, get by ID, and list operations, providing a basic CRUD foundation for pets. However, it lacks update and delete tools, which are common in such domains, and there are no tools for other potential resources or advanced operations, indicating notable gaps in coverage.