Connect your MCP client

The Omni MCP endpoint puts Omni, the agent built into every organization, behind one URL. Connect it to Claude, ChatGPT, Cursor or any MCP client and work with Omni without leaving it.

https://omni.xpander.ai/mcp

From your client you can chat with Omni across turns, start long work and poll for it, and ask Omni to task your agents, build or edit agents, manage schedules and search your organization’s knowledge. You sign in once with OAuth 2.1, and every call runs with your permissions, where systems allow.

This is not the API’s MCP endpoint (api.xpander.ai/mcp/, also OAuth 2.1), which exposes the xpander API itself and is not an agent. The Omni endpoint is scoped to you: your conversations and your access.

Calls

Call	What it does
`ask_omni`	Send Omni a message and wait. Returns the Markdown reply and a `conversation_id`.
`ask_omni_async`	Send without waiting. Returns the `conversation_id` at once.
`get_omni_task`	Status and result of a conversation started with `ask_omni` / `ask_omni_async`

Everything else (finding agents, building them, managing tasks, searching knowledge) you ask Omni for in plain words, plus the admin actions. Omni runs as you, so your own access bounds what a request can touch. For a direct connection to one agent, use the API’s MCP endpoint.

Continue a conversation

Pass the conversation_id back to ask_omni (or ask_omni_async) to continue the same thread.

You:  ask_omni("What did the support agent handle this week?")
Omni: Conversation ID: task_abc123
      This week the support agent closed 42 tickets...

You:  ask_omni("Draft a summary email to the team", conversation_id="task_abc123")
Omni: Conversation ID: task_abc123
      Here's a draft: ...

Run long work without timing out

Runs can take minutes. If one may exceed your client’s timeout, start it with ask_omni_async and poll get_omni_task until it’s done.

Admin actions

Admins can read and change organization settings over the same endpoint. Each Platform area is one call that takes an action:

Call	What it covers
`admin_members`	Members and groups
`admin_models`	Model access
`admin_budgets`	Budgets and rate limits
`admin_api_keys`	API keys
`admin_access_policies`	Access policies
`admin_audit`	Audit log and usage
`admin_runtime`	Runtime environments and locations
`admin_channels`	Channels
`admin_secrets`	Secret names and where new secrets are stored
`admin_organization`	Sharing, model gateway rules, xpander Desktop, single sign-on group links, theme and automatic top-up
`admin_tool_repo`	The Skills registry and its list of MCP servers
`admin_gateway_logs`	Model gateway request logs
`admin_projects`	Projects and who can use them
`admin_knowledge_bases`	Knowledge bases
`admin_approvals`	Approval requests

They match the Omni sidekick admin actions. Your client lists only the calls your Platform role covers, and each is checked again when it runs. Secret values and new API key values never pass through. Applied changes go to the Audit log under your name. A connection with a bare API key has no person behind it, so admin calls refuse it.

Read and change settings

Reads answer at once. A change takes two calls:

The first returns a preview (now and after) and a confirm_token. Nothing changes yet.
Call again with that confirm_token and confirm set to true to apply it, or false to drop it.

The token works once, only for you and that call, and expires after about 10 minutes.

Authentication

OAuth 2.1 only, no API key. Most clients, including ChatGPT, Claude Code, Claude Desktop and Cursor, find the sign-in from the URL and open the browser. You sign in once and the client keeps the token.

Connect from a client

Claude Code
Claude Desktop
ChatGPT
Cursor / Windsurf

Add the endpoint once from the terminal, then sign in from inside a session:

claude mcp add --transport http omni https://omni.xpander.ai/mcp

In Claude Code, run /mcp, pick omni and complete the browser sign-in. From then on, ask in plain words: “Ask Omni what my agents did today” or “Deploy this agent to xpander as a scheduled task.” On a self-hosted install, replace the address with your installation’s MCP origin.

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) and add the Omni endpoint. With OAuth, mcp-remote runs the sign-in flow the first time you start Claude:

{
  "mcpServers": {
    "xpander-omni": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://omni.xpander.ai/mcp"
      ]
    }
  }
}

Restart Claude Desktop after saving. mcp-remote opens the browser sign-in the first time. Then ask: “Ask Omni what my agents did today.”

In ChatGPT, add https://omni.xpander.ai/mcp as a remote MCP endpoint. ChatGPT runs the OAuth flow. Sign in with your xpander credentials to authorize it. Once connected, the ask_omni calls appear in its list.

Add the endpoint to your client’s MCP config with the URL https://omni.xpander.ai/mcp. The client discovers the OAuth flow from the URL and opens the sign-in on first use.

How Omni responds over MCP

MCP clients show plain Markdown, so Omni answers in self-contained Markdown and never raises an interactive card. If it needs something it can’t get here, such as a missing credential, it does what it can and tells you how to fix it in xpander Chat. If a skill needs authorization mid-run, ask_omni returns the link with the conversation_id. Authorize, then fetch the result with get_omni_task. These runs show in Session Manager tagged by client, for example “MCP - ChatGPT” or “MCP - Claude”.

Troubleshooting

Calls fail with 401 / unauthorized

The endpoint is OAuth-only and rejects x-api-key or any static key. Remove key-based config, re-add the endpoint and sign in in the browser.

Omni asks me to authorize a skill

Open the link in Omni’s reply and authorize in xpander Chat. Then call get_omni_task with the same conversation_id.

Start here

Build an agent

Company Brain

Channels

Run and monitor

xpander Desktop

Connect your MCP client

Calls

Continue a conversation

Run long work without timing out

Admin actions

Read and change settings

Authentication

Connect from a client

How Omni responds over MCP

Troubleshooting

Next steps

Call your agents over the MCP API

Learn what Omni can do

​Calls

​Continue a conversation

​Run long work without timing out

​Admin actions

​Read and change settings

​Authentication

​Connect from a client

​How Omni responds over MCP

​Troubleshooting

​Next steps

Call your agents over the MCP API

Learn what Omni can do

Calls

Continue a conversation

Run long work without timing out

Admin actions

Read and change settings

Authentication

Connect from a client

How Omni responds over MCP

Troubleshooting

Next steps