Documentation Cited By MCP
Cited By ยท MCP

Introduction

Connect AI assistants like Claude, Cursor, and other MCP-compatible tools directly to your ThriveStack data. Ask questions in plain language and get answers from the same telemetry your dashboard shows.

MCP Server

Ask your AI assistant about signups, revenue, activation, retention, accounts, and AI search visibility, and get answers straight from your ThriveStack data. This works with Claude, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, Gemini CLI, and any other MCP-compatible client.

What you can do

  • Check AI search visibility for a domain — citation gaps, competitor mentions, and content recommendations to close them, plus generate a content outline for any recommendation
  • See what buyer questions AI engines are evaluating your domain on, grouped by topic
  • See which brands/products your ThriveStack account can access
  • Run the ai_visibility_analyst prompt for a structured, one-shot analysis instead of asking one question at a time

We’re rolling out more tools incrementally — CRM accounts and leads, revenue attribution, account segments, custom SQL, and telemetry setup wizards all exist behind the scenes and are being enabled progressively. See Tools for exactly what’s callable today.

How it works

Connect

Add the server URL to your AI tool. See our setup guide for your platform.

Authenticate

Sign in via OAuth (Claude / Claude Code) or attach a Personal Access Token (every other client). This only happens once.

Ask questions or run a prompt

Ask a free-form question, or invoke one of the built-in Prompts, or pick an idea from Use Cases.

Free-form questions:

  • “Why is activation dropping this month?”
  • “What’s our MRR trend over the last 6 months?”
  • “Which accounts churned last month, and why?”

Or pick a ready-made example from Prompts or Use Cases for a full analysis.

Connection details

Your tool may ask for these details:

Property Value
Server URL https://api.app.thrivestack.ai/mcp
Transport Streamable HTTP (Remote)
Authentication OAuth 2.1 (Claude and Claude Code), or a Personal Access Token via Authorization: Bearer (any client)

Authentication

Two options, depending on what your client supports:

  • OAuth. Your AI assistant opens a ThriveStack consent page in your browser. Sign in and authorize access. The session persists across conversations. Available for Claude and Claude Code only.
  • Personal Access Token. Generate one from Personal Access Tokens (AI Visibility → Settings → Personal Access Tokens) in the ThriveStack dashboard, then attach it as an Authorization: Bearer header on your client’s MCP connection. This is the only option for Cursor, VS Code/Copilot, Windsurf, Gemini CLI, and any other client without OAuth support — not just an alternative for them.

Either way, every call resolves your product and environment automatically and respects the same permissions as your dashboard session. See the setup guide for client-by-client examples.

Read and write access

Every tool currently live is read-only — ask, the AI-visibility tools, and brand lookup all pull existing data with no side effects. See Tools for the current list.

Supported platforms

The ThriveStack MCP works with any tool that supports MCP (Model Context Protocol). Setup guides:

  • Claude (Desktop & Web)
  • Claude Code (CLI)
  • Cursor
  • VS Code (GitHub Copilot)
  • Windsurf
  • Gemini CLI

OAuth is only implemented for Claude and Claude Code today — every other client connects with a Personal Access Token. See the setup guide.

Requirements

  • A ThriveStack account with API access
  • A supported AI tool

Support

Stuck? Email support@thrivestack.ai.

Next Setup