Stape MCP Server
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., "@Stape MCP Server show me the request logs for my sGTM container"
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.
Stape.io Model Context Protocol (MCP) Server 🚀
Enterprise-grade Model Context Protocol (MCP) server for Stape.io - the leading hosting platform for server-side Google Tag Manager (sGTM) and Meta Conversions API (CAPI) Gateways.
Connect AI agents like Cursor, Claude Desktop, and Antigravity directly to your Stape infrastructure to automate container management, custom domain SSL provisioning, power-ups, request logs debugging, and Stape Store NoSQL database operations.
🌟 Key Features
18 MCP Tools: Complete coverage of Account, Invoices, Container CRUD, Custom Domains, Power-ups, Request Logs, Stats, and Stape Store (NoSQL DB).
MCP Resources: Direct access to dynamic URIs (
stape://account,stape://containers,stape://container/{id}).MCP Prompts: Pre-configured system prompt templates (
debug_gtm_container_logs,configure_custom_domain).Robust Error Boundary: Custom
StapeErrorclass returning structured JSON payloads without corruptingstdio.Security First: Isolated API Key authentication via
STAPE_API_KEYenvironment variable.Enterprise Ready: Full TypeScript type safety, Zod input validation, Vitest test suite, Docker containerization, and GitHub Actions CI.
Related MCP server: Coolify MCP Server
🛠️ MCP Tools Reference
Account & Invoices
stape_get_account_info: Retrieve account details, user profile, billing plan, and currency balance.stape_get_invoices: Retrieve billing invoices and payment history.
Container Management
stape_list_containers: List all sGTM and Meta CAPI Gateway containers.stape_get_container: Retrieve detailed configuration for a specific container by identifier.stape_create_container: Create a new sGTM or Meta CAPI container.stape_update_container: Update container settings (name, region, GTM ID, plan).stape_delete_container: Delete an existing container.
Custom Domains
stape_list_domains: List custom domains configured for a container.stape_add_domain: Add a custom domain to a container.stape_remove_domain: Remove a custom domain from a container.stape_revalidate_domain: Re-trigger DNS verification for a custom domain.
Power-ups
stape_list_powerups: List active and available power-ups (Custom Loader, Cookie Keeper, GEO Headers, Anonymizer).stape_enable_powerup: Enable a power-up on a container.stape_disable_powerup: Disable a power-up on a container.
Logs & Statistics
stape_get_logs: Fetch outgoing/incoming request logs for debugging tracking tags.stape_get_stats: Retrieve request volume statistics (daily/domain breakdown).
Stape Store (NoSQL Key-Value DB)
stape_get_store_document: Read JSON document by key from Stape Store.stape_set_store_document: Create or update JSON document by key in Stape Store.stape_delete_store_document: Remove a JSON document from Stape Store.
⚡ Quick Start & Installation
1. Prerequisites
Node.js >= 18.0.0
Stape API Key from Account settings → API Keys on stape.io.
2. Build & Test
# Clone and enter directory
cd stape-mcp-server
# Install dependencies
npm install
# Run build
npm run build
# Run unit & integration tests
npm test🔌 AI Host Configuration
Cursor Integration
Add to your Cursor MCP config (.cursor/mcp.json):
{
"mcpServers": {
"stape": {
"command": "node",
"args": [
"/path/to/stape-mcp-server/dist/index.js"
],
"env": {
"STAPE_API_KEY": "your_stape_api_key_here"
}
}
}
}Claude Desktop Integration
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"stape": {
"command": "node",
"args": [
"/path/to/stape-mcp-server/dist/index.js"
],
"env": {
"STAPE_API_KEY": "your_stape_api_key_here"
}
}
}
}🐳 Docker Deployment
# Build image
docker build -t stape-mcp-server -f deployment/Dockerfile .
# Run container
docker run -e STAPE_API_KEY="your_api_key" stape-mcp-server📄 License
MIT License - see LICENSE for details.
Available Tools
19 toolsstape_add_domainB
Add a new custom domain to a Stape container.
Inputs: domain (required), container_identifier (required).
stape_create_containerA
Create a new sGTM or Meta CAPI Gateway container on Stape.
Inputs: name (required), type (required), plan, region, +1 more.
stape_delete_containerB
Delete an existing container from Stape.
Inputs: container_identifier (required).
stape_delete_store_documentB
Delete a JSON document from Stape Store by key.
Inputs: key (required), container_identifier (required).
stape_disable_powerupB
Disable a power-up on a Stape container.
Inputs: powerup_id (required), container_identifier (required).
stape_enable_powerupC
Enable a power-up on a Stape container.
Inputs: powerup_id (required), container_identifier (required), settings.
stape_get_account_infoA
Retrieve Stape account details, user profile, billing summary, and active limits.
Inputs: no named parameters.
stape_get_containerA
Get detailed configuration and status for a specific Stape container.
Inputs: container_identifier (required).
stape_get_invoicesA
Retrieve billing invoices and payment history for the Stape account.
Inputs: no named parameters.
stape_get_logsA
Fetch outgoing request logs for a container to debug tracking tags and vendor integrations.
Inputs: container_identifier (required), type, limit.
stape_get_statsA
Fetch request volume statistics and performance metrics for a container.
Inputs: container_identifier (required), period.
stape_get_store_documentA
Retrieve a JSON document by key from Stape Store (built-in NoSQL database for sGTM).
Inputs: key (required), container_identifier (required).
stape_list_containersA
List all sGTM (server-side Google Tag Manager) and Meta CAPI Gateway containers in the Stape account.
Inputs: no named parameters.
stape_list_domainsA
List all custom domains configured for a specific container.
Inputs: container_identifier (required).
stape_list_powerupsA
List available and active power-ups for a container (Custom Loader, Cookie Keeper, GEO Headers, Anonymizer).
Inputs: container_identifier (required).
stape_remove_domainA
Remove a custom domain from a Stape container.
Inputs: domain (required), container_identifier (required).
stape_revalidate_domainB
Trigger DNS verification revalidation for a custom domain.
Inputs: domain (required), container_identifier (required).
stape_set_store_documentB
Create or update a JSON document by key in Stape Store.
Inputs: key (required), data (required), container_identifier (required), ttl_seconds.
stape_update_containerC
Update settings for an existing Stape container.
Inputs: container_identifier (required), name, plan, region, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Backend for AI agents: one batched tool over ~668 actions (hosting, storage, auth, payments).
Backend platform for AI agents: one agentstack.execute tool runs batched steps over +700 actions (hosting, storage, auth, payments, CRM, app builder).
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Coolify for complete infrastructure management including applications, databases, servers, deployments, and team operations. Provides 100% API coverage with 64 tools for managing the entire Coolify ecosystem through natural language.188 npm6MIT
- AlicenseBqualityCmaintenanceEnables control and management of Coolify self-hosted PaaS instances, allowing you to deploy applications, manage databases, monitor servers, and execute operations directly from AI assistants.8918 npm28MIT
- AlicenseCqualityDmaintenanceEnables AI agents to manage server infrastructure through the 1Panel API, including Docker containers, databases, and system monitoring. It provides tools for website management, file operations, and application deployment via natural language commands.15MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Cloudways infrastructure, including servers, applications, monitoring, and security via the Cloudways API.-