Documentation

ClimbPast MCP Server

ClimbPast exposes your GA4 and Search Console data as a set of MCP tools. Any AI agent that speaks the Model Context Protocol can use them. Authentication is a single Bearer token: your cp_ key from your dashboard.

Claude Code

Run this command in your terminal to add ClimbPast as a remote HTTP MCP server:

claude mcp add --transport http climbpast https://climbpast.com/api/mcp --header "Authorization: Bearer cp_YOUR_KEY"

Replace cp_YOUR_KEY with your API key. Create one from the dashboard, or find existing keys under Settings > API Keys.

You can also add it manually to ~/.claude.json under mcpServers with type: "http", the URL above, and an Authorization header:

{
  "mcpServers": {
    "climbpast": {
      "type": "http",
      "url": "https://climbpast.com/api/mcp",
      "headers": {
        "Authorization": "Bearer cp_YOUR_KEY"
      }
    }
  }
}

claude.ai custom connector

In claude.ai go to Settings > Integrations > Add custom connector. Fill in:

Name	ClimbPast
URL	https://climbpast.com/api/mcp
Auth type	Bearer token
Token	cp_live_your_key_here

Cursor

Add ClimbPast to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{
  "mcpServers": {
    "climbpast": {
      "url": "https://climbpast.com/api/mcp",
      "headers": {
        "Authorization": "Bearer cp_YOUR_KEY"
      }
    }
  }
}

Replace cp_YOUR_KEY with the key from your ClimbPast dashboard under Settings > API Keys.

Tool reference

All tools are read-only. ClimbPast cannot modify your GA4 or Search Console configuration.

Tool	Parameters	Description
`whoami`	none	Returns the connected workspace name, Google account, and which properties and sites are linked.
`list_properties`	none	Lists all connected GA4 properties and Search Console sites.
`get_ga4_report`	property_id, dimensions[], metrics[], start_date, end_date	Runs a GA4 report. Accepts dimensions, metrics, and a date range.
`get_ga4_realtime`	property_id	Returns active users and top pages from the GA4 Realtime API.
`get_gsc_performance`	site_url, start_date, end_date, dimensions[] (query\|page\|date)	Returns clicks, impressions, CTR, and average position from Search Console, grouped by query, page, or date.
`inspect_url`	site_url, inspection_url	Runs the Search Console URL Inspection API on a single URL.
`get_weekly_report`	none	Returns the most recent cached weekly performance snapshot for the workspace.
`get_insights`	none	Returns AI-generated insights from the latest dashboard snapshot.
`get_ai_traffic`	days (default 7)	Returns traffic attributed to AI referrers (ChatGPT, Perplexity, Claude, etc.) over a date range.

Security: how access works

You connect to ClimbPast through Google's standard OAuth sign-in flow, the same one you use to log into any trusted app with your Google account. ClimbPast is a verified Google app. It requests read-only scopes only, meaning it can read your analytics and search data but cannot change anything. Your OAuth tokens are stored encrypted in ClimbPast's database and never leave it.

Your AI agent never receives your Google credentials. It receives only a short cp_ key that authorizes it to make requests through ClimbPast's MCP server on your behalf. ClimbPast handles the Google API calls, enforces read-only scopes, and returns the results to your agent.

Revoke a cp_ key from your dashboard and it stops working immediately. Disconnect Google and all tokens and keys for that connection are deleted. You can also revoke from Google's security page at myaccount.google.com/permissions at any time. Rotate keys or cancel your subscription whenever you like.

	Your AI holds	Your AI never sees
Credential	A short revocable cp_ key	Your Google OAuth tokens
Scopes	Read-only GA4 and GSC results	Write or admin permissions
Revoke	One click from your dashboard	Anything requiring manual cleanup
Setup time	Under 2 minutes	IAM configs or credential files

Ready to connect?

$10/mo. Cancel any time.

Get started