Stape MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STAPE_API_KEY | Yes | Stape API key from Account settings → API Keys on 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 | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stape_get_account_infoA | Retrieve Stape account details, user profile, billing summary, and active limits. |
| stape_get_invoicesA | Retrieve billing invoices and payment history for the Stape account. |
| stape_list_containersA | List all sGTM (server-side Google Tag Manager) and Meta CAPI Gateway containers in the Stape account. |
| stape_get_containerA | Get detailed configuration and status for a specific Stape container. |
| stape_create_containerA | Create a new sGTM or Meta CAPI Gateway container on Stape. |
| stape_update_containerC | Update settings for an existing Stape container. |
| stape_delete_containerB | Delete an existing container from Stape. |
| stape_list_domainsA | List all custom domains configured for a specific container. |
| stape_add_domainB | Add a new custom domain to a Stape container. |
| stape_remove_domainA | Remove a custom domain from a Stape container. |
| stape_revalidate_domainB | Trigger DNS verification revalidation for a custom domain. |
| stape_list_powerupsA | List available and active power-ups for a container (Custom Loader, Cookie Keeper, GEO Headers, Anonymizer). |
| stape_enable_powerupC | Enable a power-up on a Stape container. |
| stape_disable_powerupB | Disable a power-up on a Stape container. |
| stape_get_logsA | Fetch outgoing request logs for a container to debug tracking tags and vendor integrations. |
| stape_get_statsA | Fetch request volume statistics and performance metrics for a container. |
| stape_get_store_documentA | Retrieve a JSON document by key from Stape Store (built-in NoSQL database for sGTM). |
| stape_set_store_documentB | Create or update a JSON document by key in Stape Store. |
| stape_delete_store_documentB | Delete a JSON document from Stape Store by key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug_gtm_container_logs | System prompt template for analyzing Stape outgoing request logs and diagnosing server-side GTM tracking failures. |
| configure_custom_domain | Step-by-step assistant prompt for setting up custom domains and DNS CNAME records for Stape sGTM. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Stape Account Information | Overview of Stape user account, billing plan, and currency balance. |
| Stape Containers List | JSON list of all sGTM and CAPI Gateway containers in the account. |
TDQS
Scored across 19 tools
Each tool targets a distinct action on a specific resource type (account, container, domain, powerup, logs, stats, store), with no overlapping responsibilities. For example, stape_get_container retrieves details while stape_list_containers enumerates containers, and stape_enable_powerup/stape_disable_powerup are clearly opposite operations.
Tools follow a mostly consistent stape_verb_noun pattern (e.g., stape_create_container, stape_delete_domain, stape_get_logs). Minor inconsistencies exist: plural collections use both 'list' (list_containers) and 'get' (get_invoices, get_logs), and 'set' is used for store documents instead of 'put' or 'update'.
With 19 tools, the set is slightly above the typical 3-15 range but still reasonable given the breadth of the Stape domain: containers, domains, powerups, logs, stats, store, and account management. Each tool serves a clear purpose and the count is not overwhelming.
The toolset provides comprehensive coverage for container lifecycle, domain management, power-up toggling, logging/statistics, and store document operations. Minor gaps exist, such as no ability to list all store documents or fetch a single domain's details, but these are likely edge cases.