Connect your assistant

Add Pilot as a remote MCP server, at https://app.pilot.braike.com/mcp. The connection uses OAuth: on first use, your assistant opens a Pilot page where you choose the workspace to share and what the assistant may do. No key to copy.

With the Pilot CLICopy Anchor Link

From a terminal, one command makes most of this page's settings for you:

npx @braike/pilot setup

It finds the assistants installed on your computer (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex, Gemini CLI) and registers Pilot in them, with a dated copy of each configuration before changing it. --client <name> targets a single assistant, --dry-run shows the change without writing anything. You then authorize access on the same screen, described below. Each section gives its assistant's command; every command is on The Pilot CLI.

The authorization screenCopy Anchor Link

On the first call, your assistant opens the "… is requesting access to Pilot" page on app.pilot.braike.com. Sign in to Pilot if needed, then:

1. Shared workspace: choose the workspace the assistant may read. With a workspace address, it is already chosen.
2. What the assistant can do: Read. In a Pilot MCP workspace, it is the only level offered: the screen says under the other levels that your plan is read-only.
3. Click Allow read access. Pilot sends you back to your assistant.

The application name shown is the one it declares: Pilot says so when it cannot verify it. Deny if you did not start the connection yourself. If your assistant accesses are all used, the screen says so: remove one from Manage AI accesses before authorizing the new one.

Claude (claude.ai and Claude Desktop)Copy Anchor Link

A connector added on claude.ai also works in Claude Desktop and in the mobile app: it belongs to your Claude account.

• Team and Enterprise plans: an owner of the organization first adds the connector in Organization settings, Connectors, Add, Custom, Web. Each member then connects it from Customize, Connectors.
• Free plan: Claude limits the free plan to one custom connector.
• Remove: Customize, Connectors, then Remove or the connector's … menu.

Claude Desktop, with the Pilot CLI. These commands register Pilot in Claude Desktop's configuration as a local server, connected to Pilot through the pilot mcp bridge and signed in by pilot login. Keep either the connector or this local server, not both, so as not to see Pilot twice.

npx @braike/pilot login
npx @braike/pilot setup --client claude-desktop

Source: Getting started with custom connectors using remote MCP (Anthropic).

Claude CodeCopy Anchor Link

Add the server, then sign in from Claude Code:

claude mcp add --transport http pilot https://app.pilot.braike.com/mcp

Add --scope user to get Pilot in all your projects. Then start Claude Code and type /mcp: sign-in opens in your browser. You can also run claude mcp login pilot from the terminal.

To share a project's configuration, the .mcp.json file at its root:

{
  "mcpServers": {
    "pilot": {
      "type": "http",
      "url": "https://app.pilot.braike.com/mcp"
    }
  }
}

• Sign out: claude mcp logout pilot, or Clear authentication in /mcp.
• Remove: claude mcp remove pilot, which also deletes the tokens kept by Claude Code.

With the Pilot CLI, one command makes this setting, for all your projects; then sign in with /mcp:

npx @braike/pilot setup --client claude-code

Source: Connect Claude Code to tools via MCP (Anthropic).

ChatGPTCopy Anchor Link

ChatGPT adds an MCP server as a plugin.

• Organization accounts: your ChatGPT workspace policies apply. An admin may have to allow custom MCP servers.
• Remove: open the plugin and choose Uninstall plugin, then disconnect Pilot where it was connected.

The Pilot CLI does not set up ChatGPT in the browser; for the desktop app, see Codex and the ChatGPT desktop app.

Sources: Connect and test your plugin and Plugins (OpenAI).

Codex and the ChatGPT desktop appCopy Anchor Link

Codex CLI, its editor extension and the ChatGPT desktop app share the same configuration.

codex mcp add pilot --url https://app.pilot.braike.com/mcp
codex mcp login pilot

Or in ~/.codex/config.toml:

[mcp_servers.pilot]
url = "https://app.pilot.braike.com/mcp"

In the desktop app: Settings, MCP servers, Add server, choose Streamable HTTP, paste the address, save, restart, then Authenticate.

With the Pilot CLI, one command makes this setting; then sign in with codex mcp login pilot:

npx @braike/pilot setup --client codex

Source: Model Context Protocol (OpenAI).

CursorCopy Anchor Link

The button opens Cursor with Pilot already set up. On first use, Cursor opens Pilot's authorization page. To set it up by hand, add Pilot to ~/.cursor/mcp.json (all your projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "pilot": {
      "url": "https://app.pilot.braike.com/mcp"
    }
  }
}

• Turn off: in Customize, switch Pilot off without removing it.
• Remove: delete the pilot entry from the mcp.json file.

With the Pilot CLI, one command makes this setting, in ~/.cursor/mcp.json:

npx @braike/pilot setup --client cursor

Sources: Model Context Protocol and MCP install links (Cursor).

VS CodeCopy Anchor Link

The button opens VS Code with Pilot already set up. To set it up by hand, run the MCP: Add Server command, choose HTTP and paste the address, or add Pilot to .vscode/mcp.json:

{
  "servers": {
    "pilot": {
      "type": "http",
      "url": "https://app.pilot.braike.com/mcp"
    }
  }
}

VS Code registers its client with Pilot automatically, then opens sign-in in your browser.

• Manage access: Accounts menu, Manage Trusted MCP Servers.
• Stop or remove: MCP: List Servers command, choose Pilot, then the action you need.

With the Pilot CLI, one command makes this setting, in your user profile (--client vscode-insiders for VS Code Insiders):

npx @braike/pilot setup --client vscode

Sources: Add and manage MCP servers in VS Code and MCP developer guide (Microsoft).

Any other MCP clientCopy Anchor Link

Any client that speaks MCP over Streamable HTTP connects to https://app.pilot.braike.com/mcp.

• With OAuth. The server answers 401 with a WWW-Authenticate header that points to its protected resource metadata (/.well-known/oauth-protected-resource). The client finds the authorization server there (/.well-known/oauth-authorization-server), registers (/oauth/register), then runs the flow with PKCE S256. The challenge asks for the mcp:viewer mcp:analyst scope, the Read level.
• Without OAuth, with an access key. A workspace admin creates a key in the console, For developers block. It starts with ulys_ and is shown only once. The client sends it in the Authorization header:

{
  "mcpServers": {
    "pilot": {
      "url": "https://app.pilot.braike.com/mcp",
      "headers": {
        "Authorization": "Bearer ulys_example_to_replace"
      }
    }
  }
}

A key belongs to one workspace: with the universal address, it opens its workspace. Keep it out of your code repositories and prefer an environment variable.

A client that only speaks stdio runs Pilot as a local program, through the Pilot CLI bridge, pilot mcp. Declare it in the client's configuration:

{
  "mcpServers": {
    "pilot": {
      "command": "npx",
      "args": ["-y", "@braike/pilot", "mcp"]
    }
  }
}

The bridge signs in with npx @braike/pilot login, or with an access key given in the PILOT_API_KEY variable; without a sign-in, it opens the sign-in in your browser by itself.

For any other client, npx @braike/pilot setup --client generic prints the configuration to copy. Windsurf (Devin Desktop) and Gemini CLI are also set up with the CLI; in Gemini CLI, then sign in with /mcp auth pilot:

npx @braike/pilot setup --client windsurf
npx @braike/pilot setup --client gemini

Remove an accessCopy Anchor Link

• From Pilot: on the workspace's Claude & ChatGPT page, Active access block, click Remove. A member removes their own accesses; an admin, all those of the workspace. The assistant can no longer query the workspace from its next call.
• From the assistant: remove the connector or the server, as shown for each client above.
• From the terminal: npx @braike/pilot remove --client <name> removes Pilot from an assistant's configuration, and npx @braike/pilot logout deletes the token kept by the CLI.
• When someone leaves the workspace, their assistants lose access on their next call, and their access keys are revoked on first use.