Available Tools

What Can You Do?

Aurora's MCP server gives your AI assistant access to your GEO tracking data. Here's what you can ask:

• Track your brand — Daily visibility trends for your brand and competitors across AI engines
• Measure citation share — The share of AI answers that cite each domain
• Spy on competitors — Per-competitor share of voice, the prompts they win, and the sources fueling them
• Analyze sources — Which domains and URLs AI models cite most, with source intelligence
• Read raw answers — The actual text AI engines produced for your prompts
• Use insights reports — Executive summaries and recommended actions from Aurora's insights engine
• Shopping analytics — Product win rates, rankings, destinations, and price accuracy in AI shopping answers

For complete workflow examples, see Use Cases.

Response Format

All data tools return a structured response with three sections:

{
  "metadata": { "campaign_id": "abc-123", "period": {}, "total_rows": 847, "truncated": false },
  "summary": { },
  "data": [ ]
}

Large responses are automatically truncated to stay within your assistant's context budget; metadata.truncated tells you when to paginate.

Campaign & Prompt Tools

list_campaigns

List all GEO tracking campaigns for your account. Use this first — most other tools need a campaign ID.

list_prompts

List the search prompts tracked in a campaign, including whether they are active and shopping-related. Prompt IDs feed get_prompt_performance and get_answers.

Visibility & Trend Tools

get_visibility_trend

Daily brand visibility for your brand and competitors, plus completed answers per day so you can spot sampling swings. The summary includes per-brand averages and first-vs-last deltas.

get_citation_share

The corrected citation metric: the share of completed AI answers that cite each domain (jobs_citing / total answers), overall and per day. This matches the dashboard chart.

get_brand_visibility

Row-level brand visibility entries (date × provider × prompt × brand). Prefer get_visibility_trend for time-series questions.

get_keyword_counts

Keyword frequency in AI answers, with per-keyword and per-provider summaries.

get_prompt_performance

Daily visibility, top cited domains, and keywords for a single prompt.

Competitive Tools

get_share_of_voice

Own-brand vs competitor share of voice — overall, per AI engine, plus mention-vs-citation rate and average citation position.

get_competitor_report

Per-competitor profiles: share of voice %, mentions per response, citation rate, engine mix, top prompts they win, and their source-type mix — plus the prompt × engine matrix.

Both accept campaign_id (required) and prompt_ids (optional filter). These reports aggregate the whole campaign server-side — call once and reuse the result.

Source & Answer Tools

get_citations

Citation rows showing which URLs AI engines cite, with per-domain citation-share aggregates. The deprecated per-citation visibility score has been removed.

get_sources

Cited-source report at level: "domain" (citation share + public directory info) or level: "url" (per-URL counts, providers, best position, and source intelligence: category, tier, source type, freshness, experimental source sentiment).

Note: source sentiment is judged per cited page, not per AI answer, and only a subset of URLs is enriched.

get_answers

The raw text of AI answers collected for a campaign or prompt — what ChatGPT, Perplexity, Gemini etc. actually said. Filter by provider, date range; control length with max_chars.

Insights & Shopping Tools

list_insights_reports / get_insights_report

Browse Aurora's AI-generated insights reports and fetch full sections (share of voice, prompt matrix, content briefs, owned-content audit) plus recommended actions with priority, effort, and expected impact. Use include_sections to keep responses small.

get_shopping_analytics

AI Shopping analytics: per-product visibility/win-rate/rank over time, gainers and losers, destination split, quoted-price accuracy, and query coverage. Only meaningful for campaigns with shopping prompts.

Built-in Prompts

The server also ships ready-made prompts your assistant can run:

Write Tools (opt-in)

Write access is split into two separate grants, because the two kinds of change carry very different consequences.

Write access

If you granted write access on the consent screen (or created a personal access token with write access):

Campaign creation

Creating a campaign starts recurring, billable tracking across every attached engine and counts against your plan's campaign limit. It therefore needs its own grant — write access alone is not enough, so tokens you issued before this existed cannot start that spend:

create_campaign is two-step. Called without confirm, it returns exactly what it would create plus your remaining plan headroom, and writes nothing. Only a second call with confirm: true commits.

Creating a campaign does not collect data immediately — prompts are queried on the next scheduled run.

Without the matching grant these tools are not registered at all.