WAS Stape MCP
Manage server-side Google Tag Manager containers, Conversions API gateways, custom domains, and power-ups via Stape.io.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WAS Stape MCP List all my sGTM containers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WAS Stape MCP
Production-quality shareable Model Context Protocol (MCP) server for Stape.io — standard stdio transport, zero-server setup, interactive credential CLI, cross-platform support.
Exposes 10 tools to AI assistants (Claude, Cursor, Antigravity, VS Code, Zed) for automating server-side Google Tag Manager (sGTM) containers, Conversions API (CAPI) Gateways, custom domains, and power-ups.
Prerequisites
Node.js 18+
A Stape.io account (https://stape.io)
Stape Account API Key (
Account settings->API Keys)
Related MCP server: Coolify MCP Tools
Quick start — 3 steps
Step 1 — Get your Stape API Key
Log into your Stape.io account.
Click your account name at the top right -> Account settings.
Go to API Keys -> click Create API key.
Copy your key securely.
Step 2 — Connect credentials
Run the interactive setup command:
npx -y github:was-member-keramat/was-stape-mcp authCredentials are validated against Stape.io and stored locally at ~/.was-stape-mcp/config.json with secure file permissions (0600).
Step 3 — Add to your AI client configuration
Add the following to your AI client's MCP configuration (mcpServers section):
Claude Desktop / Cursor / Antigravity Config (claude_desktop_config.json or mcp_config.json)
{
"mcpServers": {
"WAS Stape MCP": {
"command": "npx",
"args": ["-y", "github:was-member-keramat/was-stape-mcp"]
}
}
}What you can ask the AI
Here are example prompts you can use with your AI coding assistant:
Discovery: "List all my sGTM containers on Stape."
Inspection: "Show details for container ID
cnt_12345."Domains: "What custom domains are configured for my container?"
Provisioning: "Create a new sGTM container named
my-ecommerce-sgtmin theusregion."Logs & Traffic: "Show me request statistics and bandwidth usage for the past 7 days."
Power-ups: "Which power-ups are currently enabled for container
cnt_12345?"Raw API: "Run a GET call to
/v1/containerusingstape_api."
All tools (10 total)
Category | Tool Name | Description |
Account |
| Get account details, subscription plan, and usage stats |
Containers |
| List sGTM and CAPI Gateway containers |
Containers |
| Get details for a specific container by ID |
Containers |
| Create a new sGTM or CAPI container |
Containers |
| Delete or cancel a container by ID |
Domains |
| List custom domains configured for a container |
Domains |
| Add a custom domain to an sGTM container |
Analytics & Logs |
| Get request statistics and traffic bandwidth |
Power-ups |
| List power-ups enabled on a container |
Universal |
| Raw API caller escape hatch ( |
CLI commands
Command | Usage |
| Start the MCP server (used by AI tools via stdio) |
| Connect / re-connect Stape API Key |
| Display saved config location and timestamp |
| Delete saved local credentials |
| Show CLI help text |
Multi-account setup
You can override local config with environment variables (STAPE_API_KEY, STAPE_BASE_URL). This enables configuring multiple Stape accounts in your AI client:
{
"mcpServers": {
"Stape Main": {
"command": "npx",
"args": ["-y", "github:was-member-keramat/was-stape-mcp"],
"env": {
"STAPE_API_KEY": "key_main_account_token"
}
},
"Stape Client B": {
"command": "npx",
"args": ["-y", "github:was-member-keramat/was-stape-mcp"],
"env": {
"STAPE_API_KEY": "key_client_b_token"
}
}
}
}Troubleshooting
Windows Script Execution Error
If PowerShell blocks script execution:
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSignedWindows npx Cache Issues
If updates aren't pulled automatically on Windows:
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\npm-cache" -ErrorAction SilentlyContinue
npm cache clean --forceInvalid API Key Errors
Ensure you created an Account API Key (Account settings -> API Keys) and not a restricted single-container key unless you are targeting specific container scope.
License
MIT License. Free to share, remix, redistribute. Author: was-member-keramat.
Available Tools
10 toolsstape_add_domainB
Add a new custom domain to an sGTM container.
Inputs: domain (required), containerId (required).
stape_apiB
Universal escape-hatch tool to invoke any Stape API endpoint directly.
Inputs: path (required), body, method.
stape_create_containerB
Create a new server-side GTM (sGTM) or CAPI Gateway container.
Inputs: name (required), plan, type, region.
stape_delete_containerB
Delete or cancel a Stape container by container ID.
Inputs: containerId (required).
stape_get_accountA
Get Stape account details, subscription plan, and usage statistics.
Inputs: no named parameters.
stape_get_containerA
Get detailed information for a specific container by container ID or API key.
Inputs: containerId (required).
stape_get_container_logsC
Get request logs, bandwidth usage, and traffic stats for a container.
Inputs: containerId (required), days.
stape_list_containersB
List all sGTM and CAPI Gateway containers in your Stape account.
Inputs: page, type, limit.
stape_list_domainsB
List custom domains configured for a specific container.
Inputs: containerId (required).
stape_list_powerupsA
List power-ups enabled or available for a container (e.g. Cookie Keeper, Anonymizer).
Inputs: containerId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Let AI manage your Google Tag Manager containers — tags, triggers, variables, and more.
SEO & marketing toolkit for AI agents: GA4, Search Console, AdSense, GTM, PageSpeed, Trends.
60+ Meta Ads tools for AI agents: audits, campaign management, audiences and CAPI tracking.
Marketing data and actions for AI agents: GA4, Search Console, ads, social, SEO and WordPress.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Google Tag Manager, Google Search Console, and Google Analytics (GA4) through unified access to tags, search performance data, URL inspection, sitemaps, and analytics reporting.7 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Coolify infrastructure including servers, applications, databases, deployments, and 80+ one-click services through 98 comprehensive tools for both cloud and self-hosted instances.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Cloudways infrastructure, including servers, applications, monitoring, and security via the Cloudways API.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Google Tag Manager accounts, containers, workspaces, tags, triggers, variables, and versions via the Tag Manager API v2.2Apache 2.0