Setup Guide
Step-by-step instructions for connecting the ThriveStack MCP server to Claude, Cursor, and other AI tools. Stuck? Email support@thrivestack.ai.
Server URL
All platforms use the same URL:
| Endpoint | Value |
|---|---|
| Primary endpoint | https://api.app.thrivestack.ai/mcp |
Available to existing ThriveStack customers.
Authentication options
The server accepts two auth methods. Pick based on your client.
- OAuth-style authorization. The first connection redirects you to ThriveStack to sign in and approve access. Your session persists across conversations. Available for Claude (claude.ai, Claude Code) and Claude Desktop.
- x-api-key. A key tied to your ThriveStack account, sent as an
x-api-keyheader. Works with any MCP client — use this for Cursor, VS Code, Windsurf, Gemini CLI, headless setups, CI, or clients that don’t support OAuth.
Create an x-api-key
Open API Keys
Sign in to app.thrivestack.ai and go to Settings → API Keys.
Create a key
Click Create key and give it a name (e.g. “Claude Desktop”, “Cursor laptop”) so you can tell your keys apart later.
Copy the key
Copy it immediately — it’s shown only once. Treat it like a password: anyone with it can act as you via MCP.
Keys act on your account, so every call respects the same permissions as your dashboard session. Revoke a key any time from Settings → API Keys; clients using it lose access immediately.
Note: The x-api-key shown in examples on this page (d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=) is a sample demo key for trying things out before you generate your own.
Implementation instructions
Configure your MCP client to connect to
https://api.app.thrivestack.ai/mcp, then authenticate with either OAuth or an x-api-key as described above.
Claude Desktop and Web (claude.ai)
For general MCP connector setup, refer to Claude Desktop MCP servers documentation.
Option A: OAuth (recommended)
The ThriveStack connector isn’t published in Claude’s connector directory yet, so you’ll add it as a custom connector:
Open settings
Open Claude Desktop (or claude.ai) and go to Settings or Customize (gear icon), then Connectors.
Add a custom connector
Click Add custom connector and enter a name and the server URL — there’s no listing to search for yet:
- Name: Thrivestack
- URL:
https://api.app.thrivestack.ai/mcp
Authorize
Click Connect. You’ll be redirected to ThriveStack to sign in. Once authorized, return to Claude Desktop.
Only workspace admins in Claude can add a custom connector. If you’re not able to, check with your admin.
Once connected, start asking questions — ThriveStack tools will be available in MCP mode.
Option B: x-api-key
Add this to
~/Library/Application Support/Claude/claude_desktop_config.json
using this demo x-api-key:
{
"mcpServers": {
"thrivestack": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.app.thrivestack.ai/mcp",
"--header",
"x-api-key: d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g="
]
}
}
}
Claude Code (CLI)
For general MCP setup, refer to Claude Code MCP documentation.
Option A: OAuth (default)
claude mcp add -t http -s user Thrivestack "https://api.app.thrivestack.ai/mcp"
Claude Code will prompt you to authorize with ThriveStack when you first use a ThriveStack tool.
Option B: x-api-key
claude mcp add -t http -s user Thrivestack "https://api.app.thrivestack.ai/mcp" --header "x-api-key: d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g="
Then, either way:
-
Start Claude Code:
Shell
claude -
If using OAuth, enter MCP mode to authorize:
Shell
/mcp
Cursor
ThriveStack OAuth is currently available for Claude and Claude Desktop only — connect Cursor with your x-api-key. For general MCP setup, refer to
Cursor's MCP documentation.
- Open Cursor Settings, then go to Tools & Integrations > MCP.
-
Click Add Custom MCP and add the ThriveStack MCP configuration using this demo x-api-key:
JSON
{ "mcpServers": { "thrivestack": { "url": "https://api.app.thrivestack.ai/mcp", "headers": { "x-api-key": "d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=" } } } } - Select Streamable HTTP as the transport type.
VS Code (GitHub Copilot)
ThriveStack OAuth is currently available for Claude and Claude Desktop only — connect VS Code with your x-api-key.
Add a .vscode/mcp.json file to your workspace (or open the user-level config via the MCP: Open User Configuration command) using this demo x-api-key:
{
"servers": {
"thrivestack": {
"type": "http",
"url": "https://api.app.thrivestack.ai/mcp",
"headers": {
"x-api-key": "d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g="
}
}
}
}
Windsurf
ThriveStack OAuth is currently available for Claude and Claude Desktop only — connect Windsurf with your x-api-key.
- Open Windsurf Settings, then go to MCP.
-
Click Add Server and add the ThriveStack MCP configuration using this demo x-api-key:
JSON
{ "mcpServers": { "thrivestack": { "url": "https://api.app.thrivestack.ai/mcp", "headers": { "x-api-key": "d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=" } } } }
Gemini CLI
ThriveStack OAuth is currently available for Claude and Claude Desktop only — connect Gemini CLI with your x-api-key. For general MCP setup, refer to
Gemini CLI MCP server documentation.
- Ensure you're authenticated with Gemini.
-
Add this to your
~/.gemini/settings.jsonusing this demo x-api-key:JSON{ "mcpServers": { "thrivestack": { "httpUrl": "https://api.app.thrivestack.ai/mcp", "headers": { "x-api-key": "d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=" } } } } - Restart Gemini CLI to load the MCP server.
- Start asking questions; ThriveStack tools will be available in MCP mode.
Lovable Coming soon
For MCP connector setup, refer to
Lovable's MCP servers documentation. ThriveStack supports x-api-key (use sample
demo x-api-key: d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=).
- Log in to Lovable.
- Open Settings, then go to Connectors.
- Add a new MCP connector (or search for Thrivestack if available).
-
Configure the connector:
- URL:
https://api.app.thrivestack.ai/mcp - Auth header:
x-api-key=d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=(sample demo x-api-key)
- URL:
- Complete the ThriveStack connection flow in Lovable.
Other MCP clients
The ThriveStack MCP server uses Streamable HTTP transport and works with any AI tool that supports the MCP standard. Configure the
client to connect to
https://api.app.thrivestack.ai/mcp. If the client doesn’t support OAuth (currently Claude and Claude Desktop only), attach
this sample demo x-api-key as an x-api-key header:
d8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=.
- Configure your client's MCP server URL to
https://api.app.thrivestack.ai/mcp. - Ensure your client supports custom HTTP headers and set
x-api-keytod8rRhN6Ji8BGZdlVJONMm/e06k1zLkT4pHoN4LstE4g=(sample demo key). - Authenticate/connect when prompted (if your client asks for it).
- Start using ThriveStack tools in MCP mode.
Verify your connection
After setup, try asking your AI assistant:
“Is our ThriveStack setup finished, and what’s still pending?”
You should get a status response back. If that works, you’re all set. From here:
Plugins (coming soon)
ThriveStack plans to publish an MCP marketplace to extend MCP with reusable analysis and instrumentation skills. Until released, connect directly to the ThriveStack MCP server URL and use the built-in tools it exposes.
Troubleshooting
“Authorization failed” or “Unauthorized”
- Check that you signed in with the correct ThriveStack account.
- Try removing and re-adding the integration.
- Clear your browser cookies for
app.thrivestack.aiand try again. - Using an
x-api-key? Confirm the key hasn’t been revoked in Settings → API Keys, and that thex-api-keyheader is being sent.
Other issues
- Missing data: ensure your ThriveStack account has access to the target account and the data actually exists.
- Tool not found: tool availability depends on what your MCP server exposes for your account.
- Queries timing out: try smaller questions or narrower date ranges.
- Connection timeout: check your internet connection, and make sure the URL is exactly
https://api.app.thrivestack.ai/mcp.
Need help? Email support@thrivestack.ai.
Technical specifications
- Transport Type: Streaming HTTP (Remote)
- Authentication:
x-api-keyheader (sample/demo x-api-key format shown on this page) and OAuth 2.1 (Claude and Claude Desktop)