Workspaces in MCP

How one MCP connection acts across workspaces, and how to add or remove them without reconnecting.

One MCP connection can be authorized for several workspaces at once. This page covers which workspace a tool acts in, how the assistant sees your authorized workspaces, and how to add or remove a workspace after connecting.

Which workspace a tool acts in

Every connection has a default workspace, the first one you ticked when authorizing. Every tool acts there unless the call passes the optional workspace argument with the id or slug of another authorized workspace.

In practice you never think about the argument: you ask the assistant to "check the Wrap inbox in Café Bahía" and it resolves the workspace with nest_list_workspaces and passes it for you. If it names an unauthorized workspace, the error tells it which ones are, so it usually corrects itself.

How the assistant reads your workspaces

nest_list_workspaces returns the workspaces you belong to with two flags per row: current (where this call is acting) and authorized (where the connection may act). Belonging is not enough: the connection only enters the ones you authorized.

Adding a workspace to the connection

It happens in Nest, not in the assistant, and nothing needs reconnecting.

  1. In Nest open Personal, Connected apps.
  2. On the connection's row, use Add workspace and pick the workspace.
  3. Done. The connection can act there within a minute, with permissions bounded to what your account can do in that workspace.

The assistant cannot widen its own workspaces: there is no tool for it. If it asks you for access to another workspace, this screen is the way.

Removing a workspace

On the same row, each workspace's cross removes it, and the connection stops acting there within a minute. Two details:

  • If you remove the default, another authorized workspace takes over as default.
  • If you remove the last one, the whole connection is revoked, because a connection with no workspaces can do nothing.

A workspace admin can also remove that workspace from any member's connection, under Workspace, Connected apps. Only that workspace: the rest of the connection stays alive.

When reconnecting is still needed

Only four cases: the first connection, a fully revoked connection, an expired session, or asking for broader permissions than the original authorization. Changing workspaces is never one of them.