OpenAPI MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token for bearer auth. | |
| SVC_CLIENT_ID | No | Service OAuth client ID. | |
| ASANA_CLIENT_ID | No | Asana OAuth client ID. | |
| SVC_CLIENT_SECRET | No | Service OAuth client secret. | |
| ASANA_CLIENT_SECRET | No | Asana OAuth client secret. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_petD | Add a new pet to the store. |
| update_petC | Update an existing pet by Id. |
| find_pets_by_statusA | Multiple status values can be provided with comma separated strings. |
| find_pets_by_tagsB | Multiple tags can be provided with comma separated strings. Use tag1, tag2, tag3 for testing. |
| get_pet_by_idC | Returns a single pet. |
| update_pet_with_formC | Updates a pet resource based on the form data. |
| delete_petD | Delete a pet. |
| upload_fileC | Upload image of the pet. |
| get_inventoryA | Returns a map of status codes to quantities. |
| place_orderC | Place a new order in the store. |
| get_order_by_idB | For valid response try integer IDs with value <= 5 or > 10. Other values will generate exceptions. |
| delete_orderA | For valid response try integer IDs with value < 1000. Anything above 1000 or non-integers will generate API errors. |
| create_userB | This can only be done by the logged in user. |
| create_users_with_list_inputC | Creates list of users with given input array. |
| login_userC | Log into the system. |
| logout_userB | Log user out of the system. |
| get_user_by_nameA | Get user detail based on username. |
| update_userD | This can only be done by the logged in user. |
| delete_userB | This can only be done by the logged in user. |
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 19 tools
Tools are generally distinct per resource and action, but update_pet and update_pet_with_form could confuse agents expecting a single update path. Similarly, create_user vs create_users_with_list_input are similar in purpose though descriptions clarify the difference.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_pet_by_id, delete_order, create_user). There is minor variation in verbs like add vs create, but the pattern remains predictable throughout.
19 tools is well-scoped for a pet store API covering pets, users, and orders. Each tool serves a clear purpose without redundancy, and the count is within the typical range for a domain-specific server.
The toolset provides solid CRUD coverage for pets, users, and orders, including listing/filtering and file upload. Minor gaps exist—for example, no update order and no way to list all users or all pets generically—but core workflows are covered.