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: Google Webmaster MCP

Quick start — 3 steps

Step 1 — Get your Stape API Key

1. Log into your Stape.io account.

2. Click your account name at the top right -> Account settings.

3. Go to API Keys -> click Create API key.

4. Copy your key securely.

Step 2 — Connect credentials

Run the interactive setup command:

npx -y github:was-member-keramat/was-stape-mcp auth

Credentials 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-sgtm in the us region."

• 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/container using stape_api."

All tools (10 total)

CLI commands

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 RemoteSigned

Windows npx Cache Issues

If updates aren't pulled automatically on Windows:

Remove-Item -Recurse -Force "$env:LOCALAPPDATA\npm-cache" -ErrorAction SilentlyContinue
npm cache clean --force

Invalid 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.