orchestrator

Orchestrator is a prompt-first router that selects the next MCP server based on user intent.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Orchestrator.Server Catalog: Return MCP endpoints and recommended server keys.
  • Orchestrator Server Catalog: Return MCP endpoints and recommended server keys.
  • Orchestrator.Landing Routes: Public no-token routes to start the experience.

What data it sees

Do you need an account

No: the server works without sign-in

Orchestrator is a prompt-first router that selects the next MCP server based on user intent.

Core rule

  • Orchestrator never calls Nags directly.
  • Wealth/Goals can recommend switching to Nags only if the user explicitly asks to schedule reminders.

MCP servers

  • Orchestrator: https://www.getzoro.com/api/mcp/orchestrator
  • Wealth: https://www.getzoro.com/api/mcp/wealth
  • Goals: https://www.getzoro.com/api/mcp/goals
  • Nags: https://www.getzoro.com/api/mcp/nags

How it is used (typical flow)

  1. If a token is missing, start with orchestrator.landing_routes to discover public routes.
  2. If account access is needed, ask for consent and call orchestrator.send_magic_link (confirm_send=true) to email a tokenized link.
  3. For cross-domain status (what is filled vs missing), call orchestrator.summary.
  4. Based on user intent + the summary, switch to either zoro-wealth or zoro-goals for the actual work.
  5. Only if the user asks for reminder scheduling, switch to zoro-nags (usually suggested by Wealth/Goals).

How to connect

How to connect orchestrator to Claude

The server address to paste into Claude settings:

https://orchestrator--zoro.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect orchestrator to ChatGPT

The server address to paste into ChatGPT settings:

https://orchestrator--zoro.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect orchestrator to Cursor

The server address to paste into Cursor settings:

https://orchestrator--zoro.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (10)

Raw names from tools/list. Only developers need these.

orchestrator.server_catalogReturn MCP endpoints and recommended server keys.
orchestrator_server_catalogReturn MCP endpoints and recommended server keys.
orchestrator.landing_routesPublic no-token routes to start the experience.
orchestrator_landing_routesPublic no-token routes to start the experience.
orchestrator.summaryCross-domain snapshot: which goals/wealth areas have data + tokenized deep links.
orchestrator_summaryCross-domain snapshot: which goals/wealth areas have data + tokenized deep links.
orchestrator.onboardingOnboarding payload (requires token). Returns profile/shared_data + next deep links.
orchestrator_onboardingOnboarding payload (requires token). Returns profile/shared_data + next deep links.
orchestrator.send_magic_linkSend magic link email so the user can open a path with their token (uses /api/auth/send-magic-link).
orchestrator_send_magic_linkSend magic link email so the user can open a path with their token (uses /api/auth/send-magic-link).