EXO
EXO documentation

Connect your workspace to the tools where work begins.

Use EXO in the browser for cloud workspace access, or run the desktop hub when external MCP clients need controlled access to local files, repositories, and system tools.

Install desktop Open browser workspace
01

Quick start

Choose the EXO surface that matches the work you need to do.

1
Create or sign in to your EXO account

Your account carries workspace access and plan state across the browser and desktop surfaces.

2
Open the browser workspace or install desktop

Browser is best for cloud access. Desktop adds local MCP, filesystem, repository, shell, and OS-level capabilities.

3
Connect models and services from settings

Add only the providers and integrations required by your workflow. Credentials remain scoped to your account or local desktop environment.

02

Connect an MCP client

EXO Desktop exposes a local SSE endpoint for supported MCP clients while the local hub is running.

Local SSE endpoint
http://localhost:3456/sse
Desktop must be running

The endpoint is local to your machine. Keep EXO Desktop open and confirm port 3456 is available before connecting Claude Code, Cursor, Codex, Gemini CLI, or another MCP client.

Claude Code

Add EXO as a remote SSE MCP server.

Cursor

Register the endpoint in MCP settings.

Codex

Use EXO as a workspace tool provider.

Gemini CLI

Connect through its MCP server configuration.

03

Models and integrations

Keep client choice separate from model and service choice.

LayerExamplesPurpose
ModelsOpenAI, Claude, Gemini, Cerebras, local modelsReasoning and generation
AppsGoogle Workspace, Notion, Linear, AirtableExternal data and actions
Local toolsFiles, repositories, shell, MCP serversMachine-bound execution
04

Browser and desktop boundaries

Both surfaces share your account, but local machine access is intentionally desktop-only.

Browser workspace

  • Account and cloud workspace access
  • Chat, pages, tasks, and databases
  • Connected remote services

Desktop hub

  • Everything available in browser
  • Local MCP endpoint
  • Local files, shell, and OS tools
05

Security basics

Keep execution intentional and credentials narrowly scoped.

Use provider keys with only the permissions your workflow requires. Never place service secrets in client-side code.

Review requested actions before granting local file, shell, messaging, or third-party service access.

If the MCP endpoint is unavailable, confirm EXO Desktop is running and another process is not using port 3456.