integrations
integrations
Manage integrations
Usage
integrations <subcommand> [args...]
Aliases
int
Subcommands
integrations list
List your integrations
Usage:
integrations list
Options:
--json: output in JSON format
integrations setup
Set up a service integration
Usage:
integrations setup <type> [args...]
integrations setup github
Set up GitHub integration
Usage:
integrations setup github [--list|--verify|-d]
Options:
--d: disconnect GitHub account--delete: disconnect GitHub account--list: list connected GitHub accounts--verify: verify GitHub connections are working
integrations add
Add a new integration
Usage:
integrations add <type> --name=<name> [--team] [args...]
Options:
--attach: attach to a spec (vm:, tag: , or auto:all); can be repeated --bearer: bearer token (shorthand for --header="Authorization:Bearer TOKEN")--comment: optional free-form comment stored with the integration--fields: comma-separated reflection fields to expose (email, integrations, tags, comment, default_port); 'all' exposes every field including ones added in the future; 'none' disables every field--header: header to inject (e.g. X-Auth:secret)--name: integration name (required)--peer: authenticate with a generated API key scoped to the target VM--repository: GitHub repository in owner/repo format (required for github)--target: target URL (required for http-proxy)--team: create as a team integration
integrations remove
Remove an integration
Usage:
integrations remove <name>
integrations attach
Attach an integration to a VM, tag, or all VMs
A
You can attach the same integration multiple times with different specs.
Team integrations only support tag:
Usage:
integrations attach <name> <spec>
Examples:
int attach my-mcp vm:dev1
int attach my-mcp tag:production
int attach my-mcp auto:all
int attach shared-mcp tag:production
integrations detach
Detach an integration from a VM, tag, or all VMs
Usage:
integrations detach <name> <spec>
integrations rename
Rename an integration
Usage:
integrations rename <name> <new-name>