Cited By ยท MCP

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 (recommended). The first connection redirects you to ThriveStack to sign in and approve access. Your session persists across conversations. Available for Claude / Claude Desktop and Claude Code (CLI) only.
    Open the + menu in Claude, go to Connectors, then Add custom connector

    1. In Claude, open the + menu → ConnectorsAdd custom connector.

    Enter a name and the ThriveStack MCP server URL in the Add custom connector dialog

    2. Name it and enter https://api.app.thrivestack.ai/mcp, then click Add.

    ThriveStack OAuth consent screen with Agree and Allow Access button

    3. Sign in and click Agree & Allow Access on the ThriveStack consent screen.

    ThriveStack connector shown enabled in Claude's connector list

    4. You’re connected — ThriveStack tools are now available in Claude.

  • Personal Access Token (PAT). A long-lived token tied to your ThriveStack account, sent as an Authorization: Bearer header. It acts as you across every brand your account can access. This is the only option for Cursor, VS Code/Copilot, Windsurf, Gemini CLI, headless setups, CI, and any other client that doesn’t support OAuth — those clients don’t implement the OAuth flow, so a PAT is required, not just an alternative.

Create a Personal Access Token

Open the tokens page

Sign in and go directly to Personal Access Tokens (AI Visibility → Settings → Personal Access Tokens, or click “Personal access tokens” from the Connect via MCP page).

Generate a token

Click Generate new token, give it a name (e.g. “Claude Desktop”, “Cursor laptop”) so you can tell your tokens apart later, and pick an expiry.

Copy the token

Copy it immediately — it’s shown only once, as a value starting with tsmcp_. Treat it like a password: anyone with it can act as you across every brand your account can access.

A token acts on your account, so every call respects the same permissions as your dashboard session. Revoke a token any time from Personal Access Tokens; clients using it lose access immediately.

Implementation instructions

Configure your MCP client to connect to https://api.app.thrivestack.ai/mcp, then authenticate with OAuth (Claude / Claude Code only) or a Personal Access Token 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: Personal Access Token

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json, replacing YOUR_PAT_TOKEN with a token from Personal Access Tokens:

JSON
{
  "mcpServers": {
    "thrivestack": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.app.thrivestack.ai/mcp",
        "--header", "Authorization: Bearer YOUR_PAT_TOKEN"
      ]
    }
  }
}
Claude Code (CLI)

For general MCP setup, refer to Claude Code MCP documentation.

Option A: OAuth (recommended)

Shell
claude mcp add --transport http --scope user Thrivestack "https://api.app.thrivestack.ai/mcp"

Run this once, then start claude and type /mcp to sign in.

Option B: Personal Access Token

Replace YOUR_PAT_TOKEN with a token from Personal Access Tokens:

Shell
claude mcp add --transport http --scope user Thrivestack "https://api.app.thrivestack.ai/mcp" --header "Authorization: Bearer YOUR_PAT_TOKEN"

Then start Claude Code:

Shell
claude
Cursor

ThriveStack OAuth is currently available for Claude and Claude Code only — connect Cursor with a Personal Access Token. For general MCP setup, refer to Cursor's MCP documentation.

  1. Open Cursor Settings, then go to Tools & Integrations > MCP.
  2. Click Add Custom MCP and add the ThriveStack MCP configuration, replacing YOUR_PAT_TOKEN:
    JSON
    {
      "mcpServers": {
        "thrivestack": {
          "url": "https://api.app.thrivestack.ai/mcp",
          "headers": { "Authorization": "Bearer YOUR_PAT_TOKEN" }
        }
      }
    }
  3. Select Streamable HTTP as the transport type.
VS Code (GitHub Copilot)

ThriveStack OAuth is currently available for Claude and Claude Code only — connect VS Code with a Personal Access Token.

Create .vscode/mcp.json in your project (or open the user-level config via the MCP: Open User Configuration command), replacing YOUR_PAT_TOKEN:

.vscode/mcp.json
{
  "servers": {
    "thrivestack": {
      "type": "http",
      "url": "https://api.app.thrivestack.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_PAT_TOKEN" }
    }
  }
}
Windsurf

ThriveStack OAuth is currently available for Claude and Claude Code only — connect Windsurf with a Personal Access Token.

  1. Open Windsurf Settings, then go to MCP.
  2. Click Add Server and add the ThriveStack MCP configuration, using the same config as Cursor, replacing YOUR_PAT_TOKEN:
    MCP config
    {
      "mcpServers": {
        "thrivestack": {
          "url": "https://api.app.thrivestack.ai/mcp",
          "headers": { "Authorization": "Bearer YOUR_PAT_TOKEN" }
        }
      }
    }
Gemini CLI

ThriveStack OAuth is currently available for Claude and Claude Code only — connect Gemini CLI with a Personal Access Token. For general MCP setup, refer to Gemini CLI MCP server documentation.

  1. Add this to your ~/.gemini/settings.json, replacing YOUR_PAT_TOKEN:
    ~/.gemini/settings.json
    {
      "mcpServers": {
        "thrivestack": {
          "httpUrl": "https://api.app.thrivestack.ai/mcp",
          "headers": { "Authorization": "Bearer YOUR_PAT_TOKEN" }
        }
      }
    }
  2. Restart Gemini CLI to load the MCP server.
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 Code only), attach a Personal Access Token as an Authorization: Bearer YOUR_PAT_TOKEN header.

  1. Configure your client's MCP server URL to https://api.app.thrivestack.ai/mcp.
  2. Ensure your client supports custom HTTP headers and set Authorization to Bearer YOUR_PAT_TOKEN.
  3. Authenticate/connect when prompted (if your client asks for it).
  4. Start using ThriveStack tools in MCP mode.

Verify your connection

After setup, try asking your AI assistant:

“How visible is ourdomain.com in AI search right now?”

You should get a real visibility report back. If that works, you’re all set. From here:

  • Browse Use Cases for ready-made, multi-step examples.
  • Or browse Prompts for built-in analysis workflows.

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.ai and try again.
  • Using a Personal Access Token? Confirm it hasn’t been revoked under Personal Access Tokens, and that the Authorization: Bearer header is being sent.

Other issues

  • Missing data: ensure your ThriveStack account has access to the target product/environment and the data actually exists.
  • Tool not found: tool availability depends on what your MCP server version exposes.
  • 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: Streamable HTTP (Remote)
  • Authentication: OAuth 2.1 (Claude and Claude Code only) or a Personal Access Token via Authorization: Bearer header (any client)