MCP mounts

Mount one of the workspace's connected MCP servers into a Project so your agent can call its tools and read its resources.

Audience: builders

The catalog is IT's; the mount is yours. This page is the builder's binding side. For installing a server into the workspace catalog, see MCP servers.

Find the MCP servers section

Open your Project. Click the Context tab. Pick the MCP servers section. The list groups your Project view in two bands:

Mounted. Servers already bound to this Project. The chip in the section head reads <n> mounted · <m> tools once at least one is mounted.
Available. Servers IT has connected to the workspace that you can mount here. Hidden if the workspace has not connected anything yet, or if you do not have permission to mount.

The list and the right-side detail surface are scoped to this Project. Other Projects in the workspace keep their own mounts.

Mount a server

Pick a server from the Available band

Click the row to open the detail drawer. The drawer shows the server's transport, scope, and what it exposes (tools, resources). The default mount name is derived from the server's slug.

Click Mount

The mount goes live as soon as the platform reaches the server. The row moves from Available to Mounted and the detail drawer flips to the mounted view.

If the workspace has set the server's project mounts off, the row is read-only and the Mount action is hidden. Ask a workspace or team admin to enable project mounts on the catalog entry. See MCP servers for the toggle.

What a mounted server brings to the Project

Once mounted, the server's tools and resources are reachable from chat and runbooks in this Project. Tool names are namespaced by the mount name so two servers exposing the same tool do not collide.

The mounted-row chip shows the live tool count: <n> mounted · <m> tools. Click into the row for the per-server breakdown.

Refresh and unmount

The Refresh button (top right of the section head when a mounted server is selected) re-runs discovery against the server. Use it when IT has updated the upstream catalog and you want the latest tool list.

To unmount, open the server's detail drawer and click Disconnect. The action shows an inline confirm. Confirming removes the mount; the underlying catalog entry stays in place.

Mounting state versus connection state. A server can be Ready in the workspace catalog but unmounted here, or mounted here while a workspace admin has the catalog entry's Mounting toggle off. Both are valid intentional states. Disconnecting from the Project does not change the workspace credential.

When OAuth is involved

Some MCP servers require per-user OAuth. The drawer shows a Connect action when authorization is pending. Authorize once and the connection persists for your account on this server. Disconnect from the drawer revokes that authorization for your account; the mount stays in place for other users.

Calling a mounted server

From a chat conversation, ask the agent to use a tool the server exposes. From a runbook, call the tool by its namespaced name. Audit captures every tool call as a ledger entry, joined to the conversation or work item that triggered it.

For installing or configuring a server at the workspace level, see MCP servers.

Skills Integrations