Skip to content
vord Docs

Connecting External Clients

Any chat app that speaks the Model Context Protocol (MCP) can connect to vord Cloud and use the same notes, skills, and tasks your agents use. You need the vord Brain add-on on your org. Without it there is nothing to connect to.

Commands, personal tokens, and revoke live in the Hub under Connections & MCP. That Hub page links here as Documentation for external clients (/docs/cloud/external-clients/). The older Cloud page https://cloud.vord-app.dev/me/mcp-tokens redirects there.

On Overview, Connect your agents is done once at least one OAuth or personal access exists. Open guide goes to Connections & MCP.

The Brain/Chat MCP address is always the same:

https://cloud.vord-app.dev/mcp

There is no per-team address to look up. Which org a connection reaches follows the vord account you sign in with. If that account belongs to more than one org with the add-on, choose the org when sign-in asks.

vord Cloud supports Dynamic Client Registration, so an app can register itself without a client metadata document.

Connect Claude or ChatGPT

Section titled “Connect Claude or ChatGPT”

On Connections & MCP the Hub prints these commands (Claude Code and Codex) and a custom-connector path for ChatGPT and other clients:

Terminal window
claude mcp add --transport http vord-cloud https://cloud.vord-app.dev/mcp
claude mcp login vord-cloud
Terminal window
codex mcp add vord-cloud --url https://cloud.vord-app.dev/mcp
codex mcp login vord-cloud

Then sign in with your vord account, enter the email code, and allow access. On the consent page, verify Signed in as <email> · <organization>. Choose Use another account if the account is wrong. Consent is possible only when the vord Cloud sign-in is no more than five minutes old; otherwise vord Cloud signs you out and asks you to sign in again. Every new connection requires a fresh email code. The signed-in page has a Sign out button. If sign-in fails, the usual causes are a cancelled add-on, an expired or mistyped code, or an access you already revoked.

On the email-code page, Not you? Sign in with another account signs you out of the Hub and takes you to sign-in for another account.

When a vord Brain tool fails

Section titled “When a vord Brain tool fails”

Agents in vord call the same Brain tools. A failed call now returns a concrete reason instead of a blanket cloud_unavailable. Every failure is written to the app’s event log.

Retryable:

  • cloud_connecting
  • cloud_timeout
  • cloud_network
  • cloud_rate_limited
  • cloud_server_error

Not retryable:

  • cloud_off
  • cloud_device_confirmation_required
  • cloud_not_entitled
  • cloud_connection_failed
  • cloud_auth
  • cloud_request_failed

OAuth errors from vord Cloud use the standard OAuth error format.

MCP access

Section titled “MCP access”

Open Connections & MCP in the Hub. Access to vord Brain & Chat lists apps, OAuth agents, and personal tokens, with permissions and last used. Revoke takes effect immediately: the next call from that access fails, and the app has to sign in again.

External MCP that starts sessions on your Mac is the second block on the same Hub page (https://hub.vord-app.dev/mcp). Mac-side setup: Let AI apps start sessions.

See also

Section titled “See also”