Skip to main content
Detect installed MCP agents and configure them to use Ultra as their MCP server.

Usage

Flags

--agent replaces the former --client flag. --client and its -c shorthand remain as deprecated aliases and print a pointer to --agent when used.

Examples

Supported Agents

What It Does

The install command writes Ultra as an MCP server entry in the agent’s configuration. For example, Claude Desktop’s config becomes:
For Codex, the TOML config at ~/.codex/config.toml becomes:
For Hermes, the YAML config at ~/.hermes/config.yaml becomes:
Existing connectors and any non-MCP top-level keys in the Hermes config are preserved. Connectors with enabled: false are filtered out when discovering existing entries. If --config is specified, the args include --config <path>.

Auto-linking with deploy keys

Ultra auto-links the device to Hub at install time when invoked via:
  • ultra install --all — used by MDM deployments to configure every detected agent in one shot
  • ultra install --agent ona — used by the Ona devcontainer entry point, which needs the device named before any MCP agent starts
After configuring agents, these paths check for a deploy key (via ULTRA_DEPLOY_KEY environment variable, config file, or managed preferences). If a deploy key is found, the device is linked immediately:
  • The device registers with the workspace scoped by the deploy key
  • Device identity (email, external ID) is resolved from available sources (MDM preferences, environment variables)
  • The device appears in the Hub dashboard before any MCP agent launches
For all other install paths — the interactive wizard, plain ultra install --yes, and per-agent installs other than Ona — the device links during the first ultra start instead. OAuth-authenticated users always link at ultra start, regardless of which install path was used.

Backups

By default, the existing agent config is backed up before modification. Use --no-backup to skip.