AI providers and MCP
Personal and Workspace AI connections, MCP ownership, and secure runtime delivery.
Worktree keeps AI provider and MCP credentials separate from individual repositories.
AI providers
Workspace AI connections accept API keys and are available to current Workspace members. Each member can also choose their own Personal API connection. A Personal connection belongs to its owner, including when several people use the same Thread.
Manage provider connections in Settings → Providers and choose Personal or a Workspace from the scope menu. Workspace owners and administrators manage shared keys.
Cloud and shared Local Threads accept API connections only. Supported Personal OAuth connections remain available in private Local Threads. Provider groups in the model picker show Personal or Workspace.
API credentials stay in the backend vault. Model requests use scoped authorization bound to the submitting member and connection; provider credentials are injected by the broker. Revoking a connection or removing membership prevents further authorized model requests.
MCP connections
Create MCP connections in Settings → MCP under a Personal or Team scope. Open a connection to enable it only for the Workspaces that should receive it.
Worktree supports:
- Streamable HTTP: server URL, optional bearer token, and secret headers.
- STDIO: executable, separate arguments, encrypted environment variables, and an optional Workspace-relative working directory.
Direct secret values are encrypted and are not displayed again. Environment passthrough and headers sourced from runtime environment variables are not currently supported.
Where MCP servers run
- In a Local or Shared Local Workspace, STDIO servers run on the owner’s computer.
- In a Cloud Workspace, STDIO servers run inside the managed sandbox.
- Streamable HTTP connections are opened from the Workspace runtime.
Only enabled connection configuration is delivered to a runtime. Shared Local guests use the owner-hosted connection without receiving its secret, and Cloud members use the sandbox connection without receiving the stored credential.
