stape

This MCP server configuration proxys your Claude or client’s MCP requests through Stape's mcp-remote bridge. The server is exposed via an npx invocation that runs the mcp-remote package against the Stape MCP endpoint. To use it, add the stape-mcp-server entry to your Claude Desktop settings (Settings -> Developer -> Edit Config) and provide your Stape API key in place of the placeholder. When configured, Claude will forward MCP requests to https://mcp.stape.ai/mcp with the Authorization header containing your API key, enabling access to Stape’s context and tools via the MCP protocol.

If you operate in the EU region, you can enable the EU endpoint by including the additional header X-Stape-Region: EU in the same configuration. This allows Claude to route requests to the EU-specific MCP endpoint. The mcp-remote bridge handles credential storage locally, so if you encounter stale tokens or credentials, you can clear local state as described in the troubleshooting notes and restart your MCP client.

Prerequisites:

• Node.js v18 or higher (npx is included with modern Node.js/npm installations)

Installation steps:

1. Ensure Node.js is installed on your system. You can verify with: node -v npm -v

2. Install or verify npx is available (comes with npm in modern setups). npx --version

3. Prepare the MCP configuration for Claude Desktop:

   • In Claude Desktop, go to Settings -> Developer -> Edit Config.
   • Replace the content with the following JSON, and insert your Stape API key in place of ${your_stape_api_key}:

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

4. Save the configuration and restart Claude Desktop to establish the MCP connection.

Tips and caveats:

• MCP server name length: keep the server name short (e.g., stape-mcp-server) to avoid truncation by some MCP clients that have a 60-character limit for the combined server name and tool name.
• EU users: if you need EU region support, add the header X-Stape-Region: EU to the config as shown in the README.
• Credential caching: mcp-remote stores credentials locally (typically under ~/.mcp-auth). If you encounter authentication issues, you can safely remove that cache with rm -rf ~/.mcp-auth and restart the MCP client to re-authenticate.
• Ensure your Stape API key remains secret; do not commit it to shared configurations.