stape-io/stape-mcp-server

This project implements an **MCP (Model Context Protocol) server** for the **Stape** platform.
Table of Contents
- API Documentation
- Prerequisites
- Installation
- EU Endpoint Support
- Available tools
- Troubleshooting
- Useful resources
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 (v20 or higher)
Installation
The Stape MCP Server is a remote, HTTP-based MCP endpoint at https://mcp.stape.io/mcp. Clients that speak HTTP directly (Claude Code, VS Code, Copilot CLI, Cursor, Antigravity, Lovable, and Claude Desktop's custom connectors where request headers are available) connect to it as is; stdio-only clients reach it through mcp-remote, a small bridge to remote HTTP MCP servers.
> A legacy /sse endpoint also exists for backward compatibility with older SSE-based MCP clients. It isn't part of any config below — use /mcp for new integrations.
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? Each client below ends with the one change EU accounts need — see EU Endpoint Support for why.
Claude Desktop
⬇️ Click to expand ⬇️
**Custom connector (HTTP direct).** If your **Add custom connector** dialog has a **Request headers** section (in beta, not available to every organization yet):
1. Go to **Customize → Connectors → Add custom connector**. On Team and Enterprise plans, an Owner adds it under **Organization settings → Connectors** instead, and every member then uses the key the Owner entered: everyone in the organization acts as that one Stape account, including its write and delete tools, so only do this when that's intended.
2. Set the URL to https://mcp.stape.io/mcp and **Authentication** to **No sign-in**.
3. Under **Request headers**, add authorization with your Stape API key as the value, mark it **Required**, and select **Add**.
The connector also works on claude.ai. EU accounts use https://mcp.stape.io/mcp?region=eu as the URL.
**mcp-remote.** Without **Request headers**, add this to your claude_desktop_config.json (Settings → Developer → Edit Config):
EU accounts: add "--header", "X-Stape-Region: EU" to args.
Claude Code
⬇️ Click to expand ⬇️
This adds the server to the current project only. Add --scope user to use it in every project, or --scope project to write it to the project's .mcp.json (avoid that one if the file is committed, since it holds your key). Run claude mcp list or /mcp inside Claude Code to confirm it connected.
EU accounts: add --header "X-Stape-Region: EU".
VS Code
⬇️ Click to expand ⬇️
VS Code's MCP client supports HTTP servers natively, no mcp-remote needed. Add this to .vscode/mcp.json (this workspace) or to the file **MCP: Open User Configuration** opens (every workspace). VS Code asks for the API key the first time the server starts and stores it, so the key never lands in the file:
EU accounts: add "X-Stape-Region": "EU" to headers.
Copilot CLI
⬇️ Click to expand ⬇️
This writes the server entry into ~/.copilot/mcp-config.json, and it's available right away. Run copilot mcp get stape-mcp-server to confirm it connected. Inside an interactive session, /mcp add does the same through a form. See GitHub's docs for more.
EU accounts: add --header "X-Stape-Region: EU".
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, including its EU change. No separate configuration is needed.
Cursor
⬇️ Click to expand ⬇️
Cursor speaks HTTP directly too, no mcp-remote needed. Add this to .cursor/mcp.json (this project) or ~/.cursor/mcp.json (every project):