https://github.com/stape-io/stape-mcp-server
Interact with the Seape API using AI assistants like Claude, or in AI-powered IDEs like Cursor.
https://github.com/stape-io/stape-mcp-server
gtm gtm-server-side mcp mcp-server stape
Last synced: 5 months ago
JSON representation
Interact with the Seape API using AI assistants like Claude, or in AI-powered IDEs like Cursor.
- Host: GitHub
- URL: https://github.com/stape-io/stape-mcp-server
- Owner: stape-io
- License: apache-2.0
- Created: 2025-04-17T09:29:12.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2025-06-10T13:54:18.000Z (5 months ago)
- Last Synced: 2025-06-18T04:45:03.864Z (5 months ago)
- Topics: gtm, gtm-server-side, mcp, mcp-server, stape
- Language: TypeScript
- Homepage: https://stape.io
- Size: 197 KB
- Stars: 1
- Watchers: 7
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-mcp-servers - **stape-io/stape-mcp-server 📇 ☁️** - This project implements an MCP (Model Context Protocol) server for the Stape platform. It allows interaction with the Stape API using AI assistants like Claude or AI-powered IDEs like Cursor. `api` `http` `ai` `git` `github` (📦 Other)
README
# Stape MCP Server
This project implements an **MCP (Model Context Protocol) server** for the **Stape** platform.
## Prerequisites
- Node.js (v18 or higher)
## Access the remote MCP server from Claude Desktop
Open Claude Desktop and navigate to Settings -> Developer -> Edit Config. This opens the configuration file that controls which MCP servers Claude can access.
Replace the content with the following configuration (make sure npx is installed on your machine). Get Stape API key from your Stape account and set it in the configuration file instead of ${your_stape_api_key}. Once you restart Claude Desktop.
```json
{
"mcpServers": {
"stape-mcp-server": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.stape.ai/sse",
"--header",
"Authorization: ${your_stape_api_key}"
]
}
}
}
```
### Troubleshooting
[mcp-remote](https://github.com/geelen/mcp-remote#readme) stores all the credential information inside ~/.mcp-auth (or wherever your MCP_REMOTE_CONFIG_DIR points to). If you're having persistent issues, try running:
You can run rm -rf ~/.mcp-auth to clear any locally stored state and tokens.
```
rm -rf ~/.mcp-auth
```
Then restarting your MCP client.
## Open Source
The **Stape MCP Server** is developed and maintained by [Stape Team](https://stape.io/) under the Apache 2.0 license.