Skip to main content

​
Gauge MCP

The Model Context Protocol (MCP) is an open standard that lets AI clients securely connect to outside tools and data. Gauge runs an MCP server, so any MCP-compatible client — Claude, Cursor, ChatGPT, Gemini, Windsurf, Zed, or your own tooling — can query your Gauge data and take actions on your behalf, grounded in your organization’s real numbers instead of guesses. Gauge MCP uses OAuth 2.0 by default, letting you approve access from inside Gauge without managing a secret. API key authentication is also available for scripts, automation, and clients that do not support OAuth. Adding API key support does not change the existing OAuth connection flow.
Each MCP connection is scoped to one organization. OAuth connects as the user who approved access; an API key grants organization-level access without a user identity.

​
What You Can Do With It

Once connected, your client can reach across Gauge’s tools. The main categories are:
  • AI visibility and citations. Read how often your brand and competitors are mentioned or cited across AI answers, track visibility and performance over time, and see which sources and pages drive citations.
  • Topics and prompts. Browse the prompt library Gauge tracks, read individual AI answers, and curate prompts — create, generate, move, and tag them.
  • SEO and keyword reporting. Pull organic rankings, search volume and difficulty, and the keywords any domain or page ranks for, including competitors.
  • GA4, Search Console, and PostHog reporting. Run GA4 and Google Search Console reports and query PostHog where those integrations are connected.
  • Ads reporting. Read Google Ads and OpenAI Ads account summaries, campaigns, ad groups, and keyword performance.
  • Content pipeline. Run the full content workflow — create a brief, research topics, generate an outline, write and review the article, manage images, and publish to a connected CMS as a draft, to staging, or live.
  • Memory. List, read, and edit the memory files Gauge keeps about your organization.
  • Action Center. List and open recommended actions, create and assign them, set due dates, and update their status.
  • Ask Gauge. Send a natural-language question to Ask Gauge and get an answer grounded in your data.

​
Connecting Gauge MCP

The MCP integration lives under Settings → Integrations → MCP. That page has setup details for the most common clients, plus generic connection details for anything else.
1

Open the MCP integration

Go to Settings → Integrations and open the MCP card. Pick the client you use, or scroll to the generic instructions if it is not listed.
2

Add Gauge to your client

For CLI clients, copy the ready-made command. Claude Code uses Copy install command to add the server, and Codex does the same. For Claude.ai, a Claude organization admin adds Gauge as a custom connector once using Copy connector URL, and members then click Connect next to Gauge.
3

Connect any other client

For anything else, point your client at the server URL https://app.withgauge.com/mcp over HTTP (Streamable HTTP or SSE). Use Copy server URL to grab it.
4

Authorize with OAuth

The first time you use the connection, your client redirects you to Gauge in the browser. Select the organization you want and approve access.
If you work across multiple client organizations, choose the right one during the OAuth step — the client’s access is scoped to what you authorize.

​
Optional: Connect With an API Key

OAuth remains the recommended authentication method. As an additional option, use an API key when your MCP client cannot complete an OAuth flow or when the connection runs unattended. The key authenticates directly to the organization where it was created.
1

Generate an API key

In Gauge, go to Settings → Integrations → API Keys and click Generate API Key. Copy the key shown in the dialog. You can reveal it again from this page if needed.
2

Add the key to your MCP client

Configure the Gauge server URL as https://app.withgauge.com/mcp, then add this HTTP header, replacing <your-api-key> with your key:
3

Start using Gauge

Save or restart the connection as required by your client. The client can now use Gauge’s MCP tools for the organization associated with the key; no browser authorization step is required.
For example, add an API key-authenticated connection to Claude Code with:
Clients that accept JSON-based MCP configuration can use the same URL and header:
Treat an API key like a password. It grants organization-level access and is not tied to an individual user’s identity. Do not commit it to source control or share it in messages. Delete the key under Settings → Integrations → API Keys to revoke every connection using it.

​
Choose an Authentication Method

OAuth is the recommended choice for interactive AI clients such as Claude or Cursor. It keeps you signed in without storing an API key, records the user behind the connection, and lets you choose the organization during authorization. API keys are best for scripts, server-to-server automation, and MCP clients without OAuth support. They are scoped to one organization and remain active until you delete them, but requests are attributed to the organization rather than a specific user.