Can I use this server with the Stape EU environment?

Yes, include the header 'X-Stape-Region: EU' in your MCP client configuration to target the EU endpoint.

What Node.js version is required to run this server?

Node.js version 18 or higher is required.

How do I resolve issues related to cached credentials?

Clear the local MCP cache by deleting the ~/.mcp-auth directory and restarting your MCP client.

Are there any naming restrictions for MCP server configuration?

Yes, some clients limit the combined MCP server and tool name length to 60 characters; use shorter names to avoid filtering.

Stape MCP Server

MCP server enabling AI assistants to interact with the Stape API for marketing automation tasks.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "stape-io-stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

This MCP server provides an interface for AI agents to access the Stape platform API, facilitating marketing-related automation and integrations. It supports configuration for different Stape environments, including EU endpoints, via custom headers. Use this server when you want to enable AI tools like Claude or Cursor IDE to programmatically interact with Stape services through the Model Context Protocol.

Use cases

Integrate AI assistants with Stape marketing platform

Automate marketing workflows via AI-driven API calls

Configure AI tools to access Stape API with region-specific headers

Key features

Supports Stape API access via MCP protocol

Configurable authorization using API keys

EU region endpoint support with custom headers

Compatible with AI clients like Claude and Cursor

Open source implementation under Apache 2.0 license

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Stape MCP Server.

Extracted Tool Capabilities

Supports Stape API access via MCP protocol

Configurable authorization using API keys

EU region endpoint support with custom headers

Compatible with AI clients like Claude and Cursor

Open source implementation under Apache 2.0 license

Documentation Overview

Stape MCP Server

This project implements an MCP (Model Context Protocol) server for the Stape platform.

API Documentation
Prerequisites
Installation
EU Endpoint Support
Available tools
Troubleshooting
Useful resources
Open Source

API Documentation

The server wraps the Stape REST API. Full endpoint reference:

Global: https://api.app.stape.io/api/doc
EU: https://api.app.eu.stape.io/api/doc

Prerequisites

Node.js (v18 or higher)

Installation

The Stape MCP Server is a remote, HTTP-based MCP endpoint at https://mcp.stape.ai/mcp. Most clients reach it through mcp-remote, a small bridge that lets stdio-only clients talk to a remote HTTP MCP server; a few clients (VS Code, Cursor, Antigravity) speak HTTP directly.

Get a Stape API key from your Stape account and use it instead of ${your_stape_api_key} below (learn how). Restart the client after changing its config.

Using the Stape EU environment? Every config below needs one extra header — see EU Endpoint Support.

Claude Desktop

⬇️ Click to expand ⬇️

Add this to your claude_desktop_config.json (Settings → Developer → Edit Config):

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

Claude Code

⬇️ Click to expand ⬇️

Terminal

claude mcp add --transport http stape-mcp-server https://mcp.stape.ai/mcp \
  --header "Authorization: ${your_stape_api_key}"

This writes the same server entry into .mcp.json / your Claude Code MCP config. Run /mcp inside Claude Code to confirm it connected.

VS Code

⬇️ Click to expand ⬇️

VS Code's MCP client supports HTTP servers natively, no mcp-remote needed. Add this to .vscode/mcp.json:

config.json

{
  "servers": {
    "stape-mcp-server": {
      "type": "http",
      "url": "https://mcp.stape.ai/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

Copilot CLI

⬇️ Click to expand ⬇️

bash

copilot mcp add --transport http stape-mcp-server https://mcp.stape.ai/mcp \
  --header "Authorization: ${your_stape_api_key}"

This writes the server entry into ~/.copilot/mcp-config.json. See GitHub's docs for more on the copilot mcp add subcommand.

GitHub Copilot

⬇️ Click to expand ⬇️

GitHub Copilot Chat in VS Code uses VS Code's own MCP client, so it reads the same .vscode/mcp.json file — see VS Code above. No separate configuration is needed.

Cursor

⬇️ Click to expand ⬇️

Cursor speaks HTTP directly too, no mcp-remote needed. Add this to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global — Settings → MCP → Add new global MCP server):

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "url": "https://mcp.stape.ai/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

Antigravity

⬇️ Click to expand ⬇️

Antigravity also speaks HTTP directly, using serverUrl instead of url. Add this to ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — accessible from the editor's agent panel via … → MCP Servers → Manage MCP Servers → View raw config:

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "serverUrl": "https://mcp.stape.ai/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

ChatGPT

⬇️ Click to expand ⬇️

In ChatGPT, enable Developer mode: Settings → Apps & Connectors → Advanced settings → Developer mode.
Go to Settings → Connectors → Create, and set the server URL to https://mcp.stape.ai/mcp.
Authenticate with your Stape API key. ChatGPT's connector UI is OAuth-first and support for a raw Authorization header varies by rollout — if there's no field for it, use one of the other clients above instead.

Other MCP clients

⬇️ Click to expand ⬇️

Any other MCP-compatible client that expects a stdio-style command/args config can use the same mcp-remote block:

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

EU Endpoint Support

If you are using Stape EU environment, you need to provide an additional header X-Stape-Region: EU.

config.json

{
  "mcpServers": {
    "stape-mcp-server-eu": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}",
        "--header",
        "X-Stape-Region: EU"
      ]
    }
  }
}

Available tools

Each tool takes an action parameter selecting the operation (list, get, create, update, delete, …). Destructive actions additionally require confirm: true.

Area	Tools
Containers	`stape_container_crud`, `stape_container_lifecycle`, `stape_container_domains`, `stape_container_schedules`, `stape_container_power_ups`, `stape_container_proxy_files`, `stape_container_connections`, `stape_container_resources`
Monitoring & logs	`stape_container_monitoring`, `stape_container_monitoring_logs`, `stape_container_logs`, `stape_container_analytics`, `stape_container_statistics`
Billing	`stape_billing`, `stape_consolidated_invoicing`, `stape_invoices`, `stape_payment_links`, `stape_subscriptions`, `stape_container_subscription`, `stape_container_paddle`
Account & access	`stape_account`, `stape_users`, `stape_user_api_keys`, `stape_company`, `stape_share_access`
Partners	`stape_partner`, `stape_partner_payouts`
Stape Score	`stape_score_report` — scan a website's tracking setup with Stape Score (create a scan, fetch results)
Reference data	`stape_container_resource`, `stape_domains_resource`, `stape_gateway_resource`, `stape_logs_resource`, `stape_monitoring_resource`, `stape_billing_resource`, `stape_partner_resource`, `stape_products`, `stape_calculator`

Troubleshooting

MCP Server Name Length Limit

Some MCP clients (like Cursor AI) have a 60-character limit for the combined MCP server name + tool name length. If you use a longer server name in your configuration (e.g., stape-mcp-server-your-additional-long-name), some tools may be filtered out.

To avoid this issue:

Use shorter server names in your MCP configuration (e.g., stape-mcp-server)

Clearing MCP Cache

mcp-remote stores all the credential information inside ~/.mcp-auth (or wherever your MCP_REMOTE_CONFIG_DIR points to). If you're having persistent issues, clear it and restart your MCP client:

Code

rm -rf ~/.mcp-auth

Useful resources

Step-by-step guide: Stape MCP Server configuration

Open Source

The Stape MCP Server is developed and maintained by Stape Team under the Apache 2.0 license.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Marketing View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

14M

Package downloads in the last 30 days.

Last commit

1d ago

Most recent push to the default branch.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Stape MCP Server

You must provide your Stape API key in the Authorization header within your MCP client configuration.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Stape MCP Server AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/stape-io-stape-mcp-server?style=directory)](https://allmcps.com/mcp/stape-io-stape-mcp-server)

HTML Embed

<a href="https://allmcps.com/mcp/stape-io-stape-mcp-server"><img src="https://allmcps.com/api/badge/stape-io-stape-mcp-server?style=directory" alt="Stape MCP Server on AllMCPs" /></a>

Technical Specs & Signals

CategoryMarketing

10/11 checks healthy over the last 32d

56Quality signal: Good · 56/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools22/30

Adoption & activity10/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 1

Scanned 14d ago via OSV.dev · Authorization: ${your_stape_api_key} (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🎯 Marketing →Best MCP servers for Marketing →Alternatives to Stape MCP Server →Install in Claude Desktop Install in Cursor Install in VS Code

Stape MCP Server

MCP server enabling AI assistants to interact with the Stape API for marketing automation tasks.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "stape-io-stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

Use cases

Integrate AI assistants with Stape marketing platform

Automate marketing workflows via AI-driven API calls

Configure AI tools to access Stape API with region-specific headers

Key features

Supports Stape API access via MCP protocol

Configurable authorization using API keys

EU region endpoint support with custom headers

Compatible with AI clients like Claude and Cursor

Open source implementation under Apache 2.0 license

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Stape MCP Server.

Extracted Tool Capabilities

Supports Stape API access via MCP protocol

Configurable authorization using API keys

EU region endpoint support with custom headers

Compatible with AI clients like Claude and Cursor

Open source implementation under Apache 2.0 license

Documentation Overview

Stape MCP Server

This project implements an MCP (Model Context Protocol) server for the Stape platform.

API Documentation
Prerequisites
Installation
EU Endpoint Support
Available tools
Troubleshooting
Useful resources
Open Source

API Documentation

The server wraps the Stape REST API. Full endpoint reference:

Global: https://api.app.stape.io/api/doc
EU: https://api.app.eu.stape.io/api/doc

Prerequisites

Node.js (v18 or higher)

Installation

Get a Stape API key from your Stape account and use it instead of ${your_stape_api_key} below (learn how). Restart the client after changing its config.

Using the Stape EU environment? Every config below needs one extra header — see EU Endpoint Support.

Claude Desktop

⬇️ Click to expand ⬇️

Add this to your claude_desktop_config.json (Settings → Developer → Edit Config):

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

Claude Code

⬇️ Click to expand ⬇️

Terminal

claude mcp add --transport http stape-mcp-server https://mcp.stape.ai/mcp \
  --header "Authorization: ${your_stape_api_key}"

This writes the same server entry into .mcp.json / your Claude Code MCP config. Run /mcp inside Claude Code to confirm it connected.

VS Code

⬇️ Click to expand ⬇️

VS Code's MCP client supports HTTP servers natively, no mcp-remote needed. Add this to .vscode/mcp.json:

config.json

{
  "servers": {
    "stape-mcp-server": {
      "type": "http",
      "url": "https://mcp.stape.ai/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

Copilot CLI

⬇️ Click to expand ⬇️

bash

copilot mcp add --transport http stape-mcp-server https://mcp.stape.ai/mcp \
  --header "Authorization: ${your_stape_api_key}"

This writes the server entry into ~/.copilot/mcp-config.json. See GitHub's docs for more on the copilot mcp add subcommand.

GitHub Copilot

⬇️ Click to expand ⬇️

GitHub Copilot Chat in VS Code uses VS Code's own MCP client, so it reads the same .vscode/mcp.json file — see VS Code above. No separate configuration is needed.

Cursor

⬇️ Click to expand ⬇️

Cursor speaks HTTP directly too, no mcp-remote needed. Add this to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global — Settings → MCP → Add new global MCP server):

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "url": "https://mcp.stape.ai/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

Antigravity

⬇️ Click to expand ⬇️

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "serverUrl": "https://mcp.stape.ai/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

ChatGPT

⬇️ Click to expand ⬇️

In ChatGPT, enable Developer mode: Settings → Apps & Connectors → Advanced settings → Developer mode.
Go to Settings → Connectors → Create, and set the server URL to https://mcp.stape.ai/mcp.
Authenticate with your Stape API key. ChatGPT's connector UI is OAuth-first and support for a raw Authorization header varies by rollout — if there's no field for it, use one of the other clients above instead.

Other MCP clients

⬇️ Click to expand ⬇️

Any other MCP-compatible client that expects a stdio-style command/args config can use the same mcp-remote block:

config.json

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

EU Endpoint Support

If you are using Stape EU environment, you need to provide an additional header X-Stape-Region: EU.

config.json

{
  "mcpServers": {
    "stape-mcp-server-eu": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.ai/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}",
        "--header",
        "X-Stape-Region: EU"
      ]
    }
  }
}

Available tools

Each tool takes an action parameter selecting the operation (list, get, create, update, delete, …). Destructive actions additionally require confirm: true.

Area	Tools
Containers	`stape_container_crud`, `stape_container_lifecycle`, `stape_container_domains`, `stape_container_schedules`, `stape_container_power_ups`, `stape_container_proxy_files`, `stape_container_connections`, `stape_container_resources`
Monitoring & logs	`stape_container_monitoring`, `stape_container_monitoring_logs`, `stape_container_logs`, `stape_container_analytics`, `stape_container_statistics`
Billing	`stape_billing`, `stape_consolidated_invoicing`, `stape_invoices`, `stape_payment_links`, `stape_subscriptions`, `stape_container_subscription`, `stape_container_paddle`
Account & access	`stape_account`, `stape_users`, `stape_user_api_keys`, `stape_company`, `stape_share_access`
Partners	`stape_partner`, `stape_partner_payouts`
Stape Score	`stape_score_report` — scan a website's tracking setup with Stape Score (create a scan, fetch results)
Reference data	`stape_container_resource`, `stape_domains_resource`, `stape_gateway_resource`, `stape_logs_resource`, `stape_monitoring_resource`, `stape_billing_resource`, `stape_partner_resource`, `stape_products`, `stape_calculator`

Troubleshooting

MCP Server Name Length Limit

To avoid this issue:

Use shorter server names in your MCP configuration (e.g., stape-mcp-server)

Clearing MCP Cache

mcp-remote stores all the credential information inside ~/.mcp-auth (or wherever your MCP_REMOTE_CONFIG_DIR points to). If you're having persistent issues, clear it and restart your MCP client:

Code

rm -rf ~/.mcp-auth

Useful resources

Step-by-step guide: Stape MCP Server configuration

Open Source

The Stape MCP Server is developed and maintained by Stape Team under the Apache 2.0 license.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Marketing View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

14M

Package downloads in the last 30 days.

Last commit

1d ago

Most recent push to the default branch.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Stape MCP Server

You must provide your Stape API key in the Authorization header within your MCP client configuration.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/stape-io-stape-mcp-server?style=directory)](https://allmcps.com/mcp/stape-io-stape-mcp-server)

HTML Embed

<a href="https://allmcps.com/mcp/stape-io-stape-mcp-server"><img src="https://allmcps.com/api/badge/stape-io-stape-mcp-server?style=directory" alt="Stape MCP Server on AllMCPs" /></a>

Technical Specs & Signals

CategoryMarketing

10/11 checks healthy over the last 32d

56Quality signal: Good · 56/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools22/30

Adoption & activity10/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 1

Scanned 14d ago via OSV.dev · Authorization: ${your_stape_api_key} (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🎯 Marketing →Best MCP servers for Marketing →Alternatives to Stape MCP Server →Install in Claude Desktop Install in Cursor Install in VS Code

Stape MCP Server

Quick Install

Client Config & Setup

Overview

Use cases

Key features

Capabilities & Tool Schemas

Documentation Overview

Stape MCP Server

Table of Contents

API Documentation

Prerequisites

Installation

Claude Desktop

Claude Code

VS Code

Copilot CLI

GitHub Copilot

Cursor

Antigravity

ChatGPT

Other MCP clients

EU Endpoint Support

Available tools

Troubleshooting

Useful resources

Open Source

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Stape MCP Server

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Feature Your MCP Server

Own this project?

Share & Embed

Explore more

Stape MCP Server

Quick Install

Client Config & Setup

Overview

Use cases

Key features

Capabilities & Tool Schemas

Documentation Overview

Stape MCP Server

Table of Contents

API Documentation

Prerequisites

Installation

Claude Desktop

Claude Code

VS Code

Copilot CLI

GitHub Copilot

Cursor

Antigravity

ChatGPT

Other MCP clients

EU Endpoint Support

Available tools

Troubleshooting

Useful resources

Open Source

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Stape MCP Server

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Feature Your MCP Server

Own this project?

Share & Embed

Explore more