Skip to main content

Give a project's agents an MCP server

An MCP server gives agents extra tools, such as reading a design file or querying a service. A project's agent sessions reach only the MCP servers linked to it. Seeing the connection is not enough: the project has to link it.

Who can do this: anyone who can view the project sees its links. To link or unlink, you need permission to edit the project, and you must own the MCP connection or be an Org Owner or Admin.

You need an MCP connection first. If you have none, add one under Secrets: a service in the MCP servers category, or your own server (see Add a custom API or MCP server).

  1. In the sidebar, select Directory, then the Projects tab.
  2. Select the project's name to open its settings.
  3. Select the Settings tab, then MCP. With nothing linked yet, it reads No MCP server linked.
  4. Select the MCP connection field and type part of its name in Search by name. Only MCP connections you can see are listed. With none, the list says No MCP connection — add one under Secrets.
  5. Pick the connection.
  6. Select Link.
  7. Check the list: the connection is there with its server address under its name. Select the name to open the secret.

Linking also attaches the secret to the project, so its tasks may use it. The next session on the project reaches the server.

  1. Open the project's Settings › MCP, as above.
  2. Select Unlink on the connection's row.
  3. Check that the row is gone.

Once unlinked, no new session reaches the server. The secret stays attached to the project; to take it away too, see Attach a secret to a project.

What the tab shows is in the Projects reference. How secrets reach tasks is in How secrets work.