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.

Here are frequently asked questions about Conductor’s MCP server and its various connectors.
Don’t worry! While it’s easy to get caught up in the terminology, this feature is super straightforward to set up and use. You’ll just find the connector in your AI account, enter your Conductor credentials, and you’re ready to go.An MCP (model context protocol) server is just a technology that lets existing AI models (like ChatGPT or Claude) connect to data from a third-party. Conductor’s MCP server connects AI models your Conductor data, so you can query the AI model about your data.
To start, we’re making our AI data set of brand mentions, page citations, market share, and sentiment available through our MCP server. But stick around—we intend to include more data as we roll out this new technology.

​
Cool! But I don’t have the AI credits to track prompts with Conductor Intelligence’s AI Search Performance…

Now is a great time to start so that you have data to query once this feature is in a wider release! You can reach out to your Conductor representative to learn how.If adding AI credits isn’t in the cards right now, hang tight: we anticipate adding more data sets from Conductor’s Data Platform to this MCP server.
To start, we allow connections to:
  • OpenAI’s ChatGPT Pro, Business, or Enterprise plans, using an App available in their App marketplace.
  • Anthropic’s Claude Pro or Max plans, using a custom connector you can build.
No. The Conductor connector is not used to train their models. You can query your enterprise data with confidence, knowing it remains secure and private to your organization.
Standard LLMs generate answers based on training data, which is often outdated or prone to “hallucinations” (guessing). Conductor’s connector uses a Split Reasoning architecture: LLMs understand the user’s intent and handles the conversation, but Conductor’s API provides the data and facts. This ensures you get verified, accurate intelligence rather than a best guess.
Yes. While this initial release prioritizes AI and Traditional search intelligence (citations, mentions, sentiment, keyword ranks) to help you explore your visibility, we are actively building upcoming enhancements that will expand access to our other datasets—including technical website health, website analytics, and content recommendations—directly into your workflow. 
The connectors are available to Conductor customers who have access to Conductor’s MCP server in addition to a paid LLM login. You will need an active Conductor login to authenticate the connection.
Currently, the Conductor connector is available as a Free Early Access Preview for select customers. An active Conductor subscription with configured prompts in the AI Search Performance feature is currently required to be eligible for access. In the future, customers will need to add the connector to their Conductor subscription plan. 
“Local MCP” means the connection runs directly on your personal computer, whereas “remote MCP” runs in the cloud as a direct server-to-server connection. Conductor has architected our platform to support both. While we are launching our Remote MCP first to power this integration with ChatGPT, this infrastructure is universal—allowing us to easily expand our verified connector to other LLMs and interfaces (e.g., Copilot, Gemini, etc.) in the future.
Conductor’s Data API is the core infrastructure that allows you to request data programmatically for any use case—including BI dashboards, custom applications, and automated reporting. The MCP Server is a specialized connector built on top of the API that formats this data specifically for AI agents like ChatGPT and Claude. You get access to the power of both.