Orchestor MCP Server
Orchestor MCP connects AI agents to workspace data through the Model Context Protocol. Use it to inspect brands, prompts, answers, citations, and visibility reports from an MCP-compatible client.
Before you connect
You need an Orchestor account, access to a workspace, and a client that supports remote MCP and OAuth. See the client setup guide for Claude Code, Codex, Cursor, and OpenCode.
Quick setup
Register the following URL as a remote Streamable HTTP MCP server, then complete OAuth in your client.
https://mcp.orchestor.io/mcpWhat you can do
- Discover brands, topics, and prompts in a workspace.
- Read AI answers and compare visibility, citations, and sentiment.
- Find additional read-only tools through tool discovery.
- Use explicit preview and write tools when your connection has the required permissions.
Tool availability depends on the server profile and credentials. The connected client’s tools/list response is the authoritative list for that session.
Make a specific request
Start with read-only analysis in one workspace. Specify the brand, date range, and comparison. Ask the agent to include the reports or answer IDs it used.
Compare visibility and citation sources for the selected brand and date range. Include the source data and dates. Separate observations from recommendations. Do not change any data.
See MCP workflows for weekly reviews and answer investigations.
Authentication and workspace scope
Hosted OAuth associates the connection with the workspace chosen during authorization. An API key is not required for this setup. Select read permissions for reporting and analysis; a write tool requires the corresponding permission.
On the consent screen, verify the client and workspace, then choose:
| Setting | Options | How to choose |
|---|---|---|
| Access | Read-only / Read and write | Use Read-only for analysis. Select Read and write when changes are needed. |
| Grant duration | This session / Until revoked | Choose temporary access or a connection that continues until revoked. |
Select Authorize client to approve, or Deny to decline. This session expires after at most eight hours, or after 30 minutes without use.
Hosted OAuth is scoped to the authorized workspace. Tool arguments cannot grant access to another workspace.
Tool annotations distinguish reads, previews, and writes. Check the tool schema and intended changes before requesting a mutation. A tool appearing in the list does not mean the connection has permission to execute it.
Manage or disconnect a client
Open MCP connections in Orchestor to inspect connections for the current workspace. The page shows the client, access level, and grant duration.
Select Revoke for a connection you no longer need. Hosted OAuth rechecks authorization on each request, including requests in an existing session, so a revoked connection cannot continue to access the workspace. Authorize the client again if you need to reconnect.
Verify the connection
List the brands in my Orchestor workspace. Do not change any data.
A successful brands_list response verifies authentication and a read. A 401 response before OAuth indicates that authentication is required; it is not a successful connection.
Troubleshoot a connection
| Situation | What to check |
|---|---|
| The server is configured but authentication is incomplete | Start OAuth from your client and complete browser authorization. Registering the URL alone does not verify access. |
| Authentication is requested or authorization has expired | Inspect MCP connections and authorize the client again if needed. |
| Results do not match the expected workspace | Check the authorized workspace, filters, and date range. An empty list alone does not indicate an authentication failure. |
| Reads work but writes fail | Check the access level and the write tool's required inputs. |
| A tool is missing | Check tools/list and the tool reference. Tool discovery provides additional read-only tools. |
Frequently asked questions
Do I need an API key?
Not for hosted OAuth. For local execution or configurations using an existing API key, see the MCP server README.
Does a preview save data?
Hosted prompts_create only previews a prompt; it does not save it. create_issue is a write operation. Check the connected tool's schema and operation type rather than relying on its name.
Can every AI app connect?
The client must support remote MCP and OAuth. Follow the client setup guide. Installing a plugin and authorizing an Orchestor workspace are separate steps.