version: 2026-10-03 # Set up Orchestor in your agent These are the official instructions for setting up Orchestor Skills and hosted MCP. Follow only the section for the active agent and run the commands yourself. Ask the user to complete browser sign-in, OAuth consent, and reloading the running agent when needed. Configure Skills and one remote MCP server named `orchestor`. Register only `https://mcp.orchestor.io/mcp`. Skills provide task instructions; MCP provides tools for the authorized workspace. Skills that use the CLI also require the CLI installation and login below. - Set up Skills and MCP for the active agent - Optionally install the Orchestor CLI - Verify the connection with a read-only operation Back up configuration files before editing and preserve unrelated settings. Inspect and reuse existing Orchestor configuration; do not install duplicate skills or MCP entries. Never paste API keys or tokens into configuration examples, chat, or logs. --- ## Install Skills and MCP ### Claude Code Run these two commands to add Orchestor Skills and MCP together. Do not also use `npx skills` or `claude mcp add`. ```bash claude plugin marketplace add orchestor-inc/orchestor-plugin claude plugin install orchestor@orchestor ``` The plugin and its session-start hook require Node.js 24+. Check `node --version` and existing configuration first. If the `orchestor` plugin is already installed, use the update section instead of installing a duplicate. If the same skills or a manually registered MCP entry already exist, report their location and status and use one installation route. After installation, tell the user to run `/reload-plugins` inside Claude Code. Then open `/mcp` to complete Orchestor OAuth. Confirm the intended workspace and choose **Read-only** for analysis. --- ## Install for other agents For Codex, Cursor, and OpenCode, install the Skills first. ```bash npx -y skills@latest add orchestor-inc/skills --skill '*' --yes --global ``` Skip this skills command if the same skills are already installed through the Plugin or CLI. Next, use only the official configuration surface for the active client to register the remote MCP server named `orchestor`. Inspect the existing configuration before changing it. If an `orchestor` entry already exists, do not overwrite it. Report its location and status. ### Codex Register only when the `orchestor` entry does not exist. ```bash codex mcp add orchestor --url https://mcp.orchestor.io/mcp ``` If authentication is still needed, log in even when reusing an existing entry. ```bash codex mcp login orchestor codex mcp list ``` ### OpenCode — `~/.config/opencode/opencode.jsonc` If a project already uses `opencode.json` or `opencode.jsonc`, use that configuration location. Add the following entry under the existing `mcp` object. Do not replace the complete file or any other entry. ```json { "mcp": { "orchestor": { "type": "remote", "url": "https://mcp.orchestor.io/mcp", "enabled": true, "oauth": {} } } } ``` Then run: ```bash opencode mcp auth orchestor opencode mcp list ``` ### Cursor — `.cursor/mcp.json` Add the following entry under the existing `mcpServers` object. Do not replace the complete file or any other entry. ```json { "mcpServers": { "orchestor": { "url": "https://mcp.orchestor.io/mcp" } } } ``` Start Orchestor authentication from Cursor’s MCP settings and complete consent in the browser. If configuration changes are not loaded, tell the user to restart Cursor. --- ## (Optional) Install the Orchestor CLI The CLI works with brands, prompts, AI answers, and reports from the terminal. It is required for the CLI workflows in the public Skills. Ask whether the user wants to install it and skip this section if they decline. If `orc` is already installed, check `orc --version` and `orc --help` and reuse it. macOS / Linux: ```bash curl -fsSL https://orchestor.io/install | sh ``` On Windows, download the ZIP for the machine from `https://github.com/orchestor-inc/cli/releases/latest`, extract it, and place `orc.exe` on PATH. Check the CLI and log in. The user completes browser authentication. ```bash orc --version orc auth login orc workspaces list ``` Replace `YOUR_WORKSPACE_ID` with the ID the user selects from the list. Do not guess when there are multiple candidates. ```bash orc workspace use YOUR_WORKSPACE_ID orc status orc brands list --json ``` MCP and CLI authentication are separate. Completing MCP OAuth does not log in the CLI. If CLI installation was skipped, report that CLI-dependent Skills are not ready. ## Verify the connection In the agent’s OAuth flow, confirm the intended workspace and choose **Read-only** for analysis. Reload the agent and try this read: ```text Get the list of brands in Orchestor and show their IDs and names. Do not modify data. ``` A successful MCP `brands_list` call verifies the connection. An empty list is a success when no brands exist. If tools are missing, check the MCP connection and reload the agent. Do not run new measurements or writes to verify setup. Finally, report the actual Skills location and MCP configuration location. Separate configuration, authentication, and read verification. Report unrun steps, failures, and pending user actions as they are; do not mark them complete. ```text Orchestor setup result Skills: MCP: orchestor — MCP authentication: MCP read: CLI: Next action: ``` ## Update Update only the installation route in use. Review local skill edits before updating. Claude Code Plugin: ```bash claude plugin update orchestor@orchestor ``` Skills installed with the Skills CLI: ```bash npx skills@latest update ``` ## Resources - Orchestor Skills: https://github.com/orchestor-inc/skills - Orchestor Plugin: https://github.com/orchestor-inc/orchestor-plugin - Orchestor CLI: https://orchestor.io/docs/en/cli/installation - Orchestor MCP: https://orchestor.io/docs/en/mcp - Claude Code MCP: https://code.claude.com/docs/en/mcp - Codex MCP: https://developers.openai.com/codex/mcp - Cursor MCP: https://cursor.com/docs/context/mcp - OpenCode MCP: https://opencode.ai/docs/mcp-servers/ These instructions are published at https://orchestor.io/docs/en/agent-setup/prompt.md.