Use Orchestor's MCP server
Connect your AI tools to Orchestor using the Model Context Protocol (MCP). Explore brands and AI answers, compare visibility, and investigate citation sources through conversations with your agent.
Quick setup
Add this server URL to your MCP client:
https://mcp.orchestor.io/mcpThen start authentication from your client, sign in to Orchestor, and authorize access to the workspace you want to use.
What is Orchestor MCP?
Orchestor MCP is Orchestor's official MCP server. It gives AI tools remote access to your workspace without requiring you to run a server. It uses Streamable HTTP for the connection and OAuth for authentication.
Ask your agent to:
- Find brands, topics, and monitoring prompts.
- Inspect saved AI answers and their cited sources.
- Compare visibility, citation, and sentiment reports.
- Record an improvement as an Issue when you request it.
Available tools
Orchestor MCP provides tools for reading brands, answers, and reports, as well as discovering additional read tools by purpose. The tools reference lists tools by category with their inputs and sample requests.
Available operations depend on the server configuration and your connection's permissions. For example, prompts_create previews a prompt, while create_issue creates an Issue. A prompt preview does not save the prompt.
Connect to Orchestor MCP
You need an Orchestor account with access to the workspace. Your client must support remote MCP and OAuth. You do not need to configure an API key for this connection.
Setup guides are available for:
Set up your client
Claude Code
Add the MCP server from your terminal:
claude mcp add --transport http orchestor https://mcp.orchestor.io/mcpStart Claude Code, open /mcp, and authenticate orchestor. Confirm the workspace and permissions in your browser, then authorize access.
Codex
Add the server to ~/.codex/config.toml:
[mcp_servers.orchestor]
url = "https://mcp.orchestor.io/mcp"Authenticate and check the server registration:
codex mcp login orchestor
codex mcp listCursor
Add the server to your project's .cursor/mcp.json. If the file already contains servers, add orchestor to the existing mcpServers object.
{
"mcpServers": {
"orchestor": {
"url": "https://mcp.orchestor.io/mcp"
}
}
}Start authentication for orchestor from Cursor's MCP settings and authorize access in your browser.
Try the connection
Ask your connected agent:
List the brands in my Orchestor workspace. Include each brand's ID and name.
A successful brand-list response completes your first read. An empty list is expected if you have not added brands. Next, specify a brand and date range:
Review this brand's visibility and citation sources over the last 30 days. Include the supporting reports and AI answers. Separate observations from recommendations.
See use cases for more sample requests.
Manage access and connections
On the consent screen, check the client and workspace. Choose Read-only for analysis or Read and write for changes such as creating an Issue. Choose This session or Until revoked for the connection duration.
Access is limited to the workspace selected during authorization. To use another workspace, authorize a connection to that workspace.
Open MCP connections to inspect or disconnect a client. Select Revoke to prevent that connection from accessing the workspace.
Troubleshooting
| Situation | What to do |
|---|---|
| The server is added but cannot read data | Start authentication from your client and authorize workspace access in your browser. |
| Authorization has expired | Authenticate again from the client. Check the connection in MCP connections. |
| The expected data is missing | Check the authorized workspace, target brand, and date range. |
| Reads work but creating an Issue fails | Check that the connection has Read and write access. |
| A tool is missing | Check its purpose in the tools reference and ask the agent to inspect the available tools. |