Skip to main content

Documentation Index

Fetch the complete documentation index at: https://conductor.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Conductor’s MCP server connects your Conductor account to AI assistants (such as ChatGPT or Claude) through connectors. You ask questions in natural language; the assistant uses MCP tools to read allowed Conductor data and answer from your metrics—not generic SEO advice. The MCP spans two broad areas of your Conductor data: AI search (how your brand shows up in AI-generated answers) and traditional search (how your site ranks in classic search engine results). You can analyze each on its own or ask the assistant to connect the two—for example, comparing where you rank traditionally against where you’re mentioned and cited in AI search. For connector setup, use the Getting Started pages in this MCP section.

What kinds of questions can you ask?

The conversational interface is meant to help you probe your data and surface insights you might not have clicked to in the product. For example:
What are the topics in AI search where my site is cited most? Which pages are cited the most? How am I performing on my tracked prompts compared to competitors? What topics should I prioritize for content optimization? What topics might I consider tracking in Conductor that I do not track yet?
For traditional search, you can probe rankings, demand, and the SERP itself:
Which of my tracked keywords improved or declined in rank over the last quarter, and which keyword groups are driving the change? Where are competitors outranking me, and which keywords show the biggest gaps? Which keywords are seasonal, and when should I publish to catch the next demand peak? For my priority keywords, which SERP features (People Also Ask, Local Pack, and others) appear, and how should that change my content format?
You can iterate from there—the assistant can help you refine questions as you learn what the tools return.

Tools and analysis areas

The MCP exposes focused tools (named capabilities the model can call) that align with datasets in Conductor Intelligence, across both AI search and traditional search:

AI search analysis

These capabilities focus on how your brand (and competitors) show up in AI-generated answers across supported AI search engines.

Brand mention analysis

Tools and prompts here focus on how your brand (and competitors) show up in AI search performance data—often discussed as brand mentions. Useful angles include:
  • Topics and prompts: Which topics or queries (in the data, a tracked prompt is treated as a query) drive the most brand mentions for you, including unbranded queries where you still appear.
  • Competition: Share of voice vs competitors, queries where you lead or trail, simple charts (for example pie charts) when the assistant can build them from tool output.
  • Over time: How brand-mention share of voice has trended.
  • Persona and intent: Strongest and weakest areas by persona or search intent (as modeled in Conductor).
When you ask, use the phrase “brand mention” so the model routes to the right tools and framing. You can also ask whether actual AI response snippets are available where you have brand mentions; that slice of the experience may still be coming online depending on your program version—confirm with your assistant or Conductor contact if you need raw snippet text.

Citation analysis

A separate set of capabilities focuses on citations: which URLs and domains AI engines cite as sources. You may see tool names such as ai_citations_marketshare in explanations or logs. Typical questions include citation share vs competitors, topics or queries where you are mentioned but not cited, performance over time, and breakdowns by persona or intent.

Sentiment analysis

Sentiment tooling helps you understand how AI responses talk about your brand in connection with tracked prompts. Sentiment analysis applies to your own AI responses within the supported scope; you can still ask the assistant to compare or contextualize you vs competitors for brand mentions in other flows. Prompts often combine topics, queries, time trends, persona, and intent.

Traditional search analysis

These capabilities focus on how your site performs in classic search engine results for your tracked keywords. Use the phrase “traditional search” (or “keyword rankings”) so the model routes to the right tools.

Rankings and visibility

Ask where you rank and whether it’s improving—across your whole keyword set or any slice of it. Useful angles include:
  • Rank trends: How rankings have moved over time for individual keywords or keyword groups, and where you’ve won or lost visibility.
  • Segments: Performance by keyword group or location/market, so you can prioritize the keywords and regions that need attention.

Seasonality and demand

Ask about monthly search volume trends (typically the last 24 months) to separate ranking changes from shifts in underlying demand. This helps you explain why visibility or traffic moved and time content and campaigns to seasonal peaks.

Result types (SERP features)

Ask which SERP features make up a keyword’s results—Standard Links, People Also Ask, Local Pack, and others. This explains why ranking well doesn’t always drive clicks and points to concrete content-format recommendations.

Competitive rankings

Ask how you stack up head-to-head against competitor domains (up to three) for your tracked keywords. The assistant can identify where rivals are pulling ahead and ground gap analysis in real position data.

Keyword deep dives

Ask about a single keyword to move from account-wide summaries to specifics: a rank snapshot, week-by-week rank history, monthly search volume trend, and the full SERP for that term.

Account configuration

You can let the LLM review your current configuration—topics, prompts, brands, competitors, personas, intents, locales, search engines, and tracked keywords—to discover gaps or review your tracking strategy across both AI and traditional search.

Discovery prompts (learn what you have access to)

Before deep analysis, you can inventory what the connection can see—still in plain language:
  • Show me which Conductor accounts I have access to.
  • Use [account name and ID] for further analysis.
  • Show me the tools and data I have available via Conductor.
  • What time ranges does Conductor data cover for me?
These reduce guesswork before you dig into deeper analysis.

Use vocabulary Conductor already uses

Vague words like “visibility” are easy for humans but ambiguous for tools. Prefer product language. For AI search: brand mentions, citations, topics, queries (for tracked prompts), personas, intents, and competitors by name when comparing. For traditional search: keywords, keyword groups, rankings (or rank), search volume, seasonality, SERP features (such as People Also Ask and Local Pack), and locations. You will get clearer tool use and answers.

Access and configuration

If your user and organization have not been granted MCP Early Access, you may still be able to add a connector, but you will not be able to query Conductor data through it. For ChatGPT- or Claude-specific configuration, contact your Conductor team for instructions that match your program.

What to keep in mind

  • Access and privacy follow your org’s rules; tools only return what your account is allowed to see.
  • Validate important decisions; the assistant summarizes and explores—it does not replace your judgment or governance.
  • Review our template gallery for ideas of how to apply the MCP with LLM skills to deepen the analysis and insights.
  • Ask your Conductor team for updated prompt examples, recommendation-style wrap-ups, and citation-specific patterns.