MCP Server: SaaS Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXAMPLE_API_TOKEN | Yes | API token for the example app. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gateway_list_appsA | List all SaaS apps wired into this gateway, with their type and configuration status. |
| example_get_resourceB | Fetch a resource from the Example API by ID. |
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 2 tools
The two tools have clearly distinct purposes: one fetches a resource by ID, the other lists all apps configured in the gateway. There is no overlap in functionality.
Both tools follow a consistent verb_noun pattern using snake_case (example_get_resource, gateway_list_apps), maintaining predictable naming.
With only 2 tools, the server is at the low end of the borderline range. While not extreme, it feels thin for a SaaS gateway that would typically require more operations.
The tool set is missing essential CRUD operations for resources, app management (create, update, delete), and configuration details. Agents would fail when trying to perform common gateway tasks.