Skip to main content
AthenaHQ ships a remote Model Context Protocol (MCP) server. Once connected, an AI assistant like Claude or ChatGPT can query your AI search visibility data in plain language (share of voice, citation and mention rates, ranking positions, cited sources, tracked prompts and responses, content, and pitches) without you writing any API calls. Connections you sign in to (Claude.ai and ChatGPT) read the same data your account can already see. Write tools are available on API-key connections and, for signed-in connections, wherever your role has the matching write permission. Every write runs the same validation and audit logging as the dashboard. Server URL

Connect Claude.ai

No API key needed. You sign in with your AthenaHQ account.
1

Open connector settings

In claude.ai, go to Customize → Connectors → the ”+” → Add custom connector.
2

Paste the server URL

Enter https://api.athenahq.ai/api/mcp and continue.
3

Sign in and pick an organization

You’ll be prompted to sign in with your AthenaHQ account and choose which organization to connect. Claude then discovers all available tools automatically.

Connect ChatGPT

The fastest way is the official AthenaHQ plugin. No API key needed. You sign in with your AthenaHQ account.
1

Install the plugin

Open the AthenaHQ plugin listing in ChatGPT and click Install plugin.
2

Sign in and pick an organization

Authorize with your AthenaHQ account and choose which organization to connect.
3

Mention @AthenaHQ in a chat

Type @AthenaHQ followed by your question, for example “@AthenaHQ how is my brand showing up in AI search?”, and ChatGPT pulls your data into the conversation.
Prefer a manual setup? You can still add the MCP server as a custom connector: in ChatGPT Settings, add a custom MCP connector (found under Apps or Connectors, depending on your plan and version), enter https://api.athenahq.ai/api/mcp, and sign in with your AthenaHQ account. Custom connectors require a plan that supports them (Pro, Business, or Enterprise) and may need developer mode enabled.

Connect other MCP clients

Clients that don’t support the sign-in flow authenticate with an API key using the x-api-key header.
1

Create an API key

Go to the API Keys page in your dashboard. Scope the key to specific websites if you want to limit access, then save it securely.

Manage API Keys

Create, view, and manage API keys in your organization settings
2

Add the server to your client config

Replace your_api_key_here with your key.

Claude Code

Access and scope

An MCP connection sees exactly what its credential is authorized for, the same scoping as the REST API:
  • Organization and website access follow the signed-in user (Claude.ai) or the API key’s scope.
  • A website-scoped API key is limited to its websites, with one deliberate exception: organization-level tools (such as get_credits_organization) return org-wide aggregates. Each tool applies the same authorization as its REST endpoint.
  • Write tools register on API-key connections and on signed-in connections bound to an organization. On a signed-in connection, each write is gated by your role’s permission for that category (see the Write tools table); API keys act with admin privileges within their scope. Every write runs the same validation and audit logging as the dashboard.
Only organization admins can create, edit, or delete API keys. On signed-in connections, tools follow your role: a viewer can read everything below except the three org-wide admin reads (get_groups, get_group_detail, get_user_by_email), and can only use writes open to every member (such as create_saved_view).

Available tools

The assistant discovers these automatically once connected. Most map to an endpoint in the API reference.

Metrics

Analytics queries

Flexible query tools over the same analytics warehouse the dashboard uses, for questions the fixed metrics tools don’t cover.

Attributes

Brand-perception keywords (like “Affordable” or “Slow Support”) extracted from AI answers.

Prompts and responses

Content

Knowledge Base

Requires the Knowledge Base to be enabled for the organization; when it isn’t, these tools return an error explaining that.

Sources and competitors

Pitches

Account and configuration

Site diagnostics

Write tools

Available on API-key connections and on signed-in connections bound to an organization. On a signed-in connection, each tool follows your role’s permission for its category (rightmost column); API keys act with admin privileges within their scope. Every write is validated and audit-logged, same as the dashboard. create_saved_view is the one write open to every website member, since saved views are personal presets: sign-in creations are attributed to the connected user, while API-key creations have no owning user, show as created via API in the dashboard, and can only be edited or deleted there by website admins. It is also the one write tool with no REST equivalent.

Example prompts

Once connected, try:
  • “What’s my share of voice in AI answers versus my tracked competitors this quarter?”
  • “Which domains get cited most for the prompts I track?”
  • “Show my citation rate trend over the last 90 days.”
  • “What’s my captured AI search value and headroom by topic?”
  • “Pull the AI responses that mention my brand and summarize their sentiment.”