WAS Stape MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STAPE_API_KEY | Yes | Your Stape Account API key | |
| STAPE_BASE_URL | No | Optional base URL for Stape API (default: https://api.stape.io) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stape_get_accountA | Get Stape account details, subscription plan, and usage statistics. |
| stape_list_containersB | List all sGTM and CAPI Gateway containers in your Stape account. |
| stape_get_containerA | Get detailed information for a specific container by container ID or API key. |
| stape_create_containerB | Create a new server-side GTM (sGTM) or CAPI Gateway container. |
| stape_delete_containerB | Delete or cancel a Stape container by container ID. |
| stape_list_domainsB | List custom domains configured for a specific container. |
| stape_add_domainB | Add a new custom domain to an sGTM container. |
| stape_get_container_logsC | Get request logs, bandwidth usage, and traffic stats for a container. |
| stape_list_powerupsA | List power-ups enabled or available for a container (e.g. Cookie Keeper, Anonymizer). |
| stape_apiB | Universal escape-hatch tool to invoke any Stape API endpoint directly. |
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 10 tools
Most tools have distinct purposes (account, containers, domains, logs, powerups). However, the generic stape_api tool blurs boundaries, potentially causing misselection when a specific tool exists.
All tools follow the stape_<verb>_<noun> pattern except for stape_api, which breaks the convention. The rest are consistent and predictable.
10 tools cover the main aspects of Stape account and container management without being overwhelming. Each tool serves a clear purpose.
The set covers basic CRUD for containers and domain listing but lacks update/delete for domains, manage powerups, or update containers. The generic stape_api can fill gaps but the official tool surface has notable omissions.