Skip to main content
Plugins, MCP and Skills extend what the agent can do: plugins can include commands and hooks; MCP servers connect the agent to external tools; a Skill is a set of instructions written for the agent. All three are managed under Settings › Integrations › Plugins, and cloud sessions load the enabled items when they start. Services that require signing in to a third-party account (GitHub, Gmail, Notion and others) are not managed here. You authorize them in Connectors.

Availability

Where to find it

  • Settings › Integrations › Plugins.
  • The plugins entry in a machine’s details under Settings › Machines opens the same page with that device preselected.

Key concepts

Plugin libraries are separate for each workspace. Cloud switches and the switches on each device are independent: turning off an item on a device does not affect the item with the same name in Cloud shared, and vice versa.

List

The page toolbar has Location, search, Add and Sync from device. Below it, items are listed under the tabs All, Plugins, Skills and MCP. Each item shows its name, scope (Cloud shared or Device only), version, source and enable switch. Plugins with hooks are marked Includes hooks.
  • Switches affect only sessions that start afterward. Cloud sessions load the new setting on their next turn.
  • A device’s switches can only be changed in the app on that device. Everywhere else they are read-only.

Details

Click a name to open the details, where you can see the description, where it is available, and its source.
  • For a Cloud shared item, click Stop sharing: new cloud sessions no longer load it, and device installations and local switches stay as they are. MCP items also have Edit configuration.
  • For a device item, click Sync to workspace to open Sync from device with this item preselected.

Add and import

Click Add in the toolbar to open Add to library. Currently, only adding MCP servers to Cloud shared is supported (by importing JSON or configuring manually). File import for plugins and Skills, and adding to a device, are coming soon.

Import MCP JSON

  1. In Add to library, select MCP, with the location set to Cloud shared.
  2. Choose or drag in a JSON file (the mcpServers format is supported, as is a single server’s url / command configuration).
  3. Check the server names and URLs or start commands in the preview.
  4. Click Import N items. Imported items are disabled by default. Enable them from the list when needed.
If the import fails, the dialog states the reason (for example invalid JSON or an incomplete URL). Fix the file as described, then import again.

Add or edit an MCP server

In Add to library, select MCP and click Configure MCP manually in the lower-left corner. To edit an existing server, open the MCP details in Cloud shared and click Edit configuration. When editing, Delete in the lower-left corner removes the server. First enter the Name (it cannot be changed when editing), then choose the Type: Values for environment variables, tokens and headers cannot be plaintext. They can only be variable names from Secrets & variables, and the fields suggest secret names that already exist in the workspace. Manually added MCP servers are enabled by default.

Sync from device

Upload plugins, Skills and MCP servers already installed on a device to the workspace so cloud sessions can use them too. Scanning and uploading can only be done in the desktop app on that device.
  1. In the desktop app, click Sync from device in the toolbar.
  2. Source device defaults to this device. Click Scan device.
  3. When the scan finishes, select the items to sync (none are selected by default, and unselected items stay only on this device).
  4. Handle version conflicts, hooks and secrets as needed (see below).
  5. Click Sync selected. When done, cloud sessions load the items on their next turn, and installations and switches on the device are unchanged.
When some items fail to sync, the result lists the reason for each item. Click Retry incomplete to retry only the failed items.

Items you cannot select

Version conflicts and hooks

  • When a selected item already has a different version in the cloud, choose one: Keep cloud version (default, this item is not uploaded) or Use device version (replaces the old cloud version).
  • When selected plugins include hooks (which can run commands automatically before or after tool calls), you must check Allow selected plugin hooks to run in cloud tasks to sync.

Notes and limits

  • The first release offers only a plugin library at the personal workspace level. There is no plugin marketplace.
  • Currently you can add only Cloud shared MCP servers directly. Plugins and Skills can be uploaded with Sync from device.
  • MCP configurations cannot contain plaintext secrets. They can only reference variables in Secrets & variables.

FAQ

What is the difference between “Cloud shared” and “Device only”?

Cloud shared items are uploaded to the workspace, and all cloud sessions can use them. Device only items stay on that device, and only sessions that run on that device can use them.

Why did an import not take effect?

Imported MCP servers are disabled by default. Turn on the switch in the list. Cloud switches are loaded on the session’s next turn.

Why can’t an MCP server be synced to the cloud?

It depends on a local path on the device (or localhost), or its configuration contains a plaintext secret. For the first case, change it to a configuration that can be accessed remotely. For the second, use Use secret reference and change the configuration to a variable reference on the device, then sync.

Why can’t I scan a device from the web?

Scanning reads files on the device itself, so it can only be done in the desktop app on that device.