Skip to main content

Grant MCP servers and profiles to a project

Enterprise Tier

A project controls which Model Context Protocol (MCP) servers it can use and exposes them to AI clients through MCP profiles. MCP is a standard for connecting AI clients to external tools and data sources. Scoped to a project, MCP falls under the same isolation as models: a project sees only its own servers, and its profiles are reachable only through its own gateway with its own keys.

An MCP server is an adapter that exposes a tool or data source to AI clients; an MCP profile aggregates one or more servers behind a single endpoint that clients connect to once. Granting MCP to a project makes the project the boundary for tools in exactly the way it is the boundary for models. This guide grants servers to a project and builds a profile on the project's gateway.

Persona: Platform operator or project administrator working in the Admin Dashboard.

Estimated time: 15--25 minutes for the first profile.

Outcomes​

By the end of this guide:

  • The MCP servers a project may use are granted to it.
  • A profile that bundles the chosen servers is published on the project's gateway.
  • The profile's isolation is understood: it is reachable only with the project's key, through the project's gateway.

Prerequisites​

  • Membership of the project, with permission to manage its MCP configuration.
  • A gateway provisioned for the project, so the profile has an endpoint. See Provision a gateway for a project.
  • The MCP servers available in the organisation's catalog. Cataloguing and governing servers is covered in Govern MCP server access.

Step 1: Grant MCP servers to the project​

  1. Use the project switcher to select the project.
  2. Open MCP Servers and enable the servers this project may use.

A project can see and use only the servers granted to it. A server that is not granted is neither listed for the project nor callable through it, which is what keeps one project's tools separate from another's.

Step 2: Build an MCP profile​

A profile bundles one or more of the project's granted servers into a single endpoint an MCP client connects to.

  1. In the project, open My MCP Profiles and select Add MCP Profile, then name it.
  2. Select Add Server, choose from the servers granted to the project, and enable the tools wanted from each.
  3. Set the profile's authentication, either API key or OAuth.

The profile is published on the project's gateway, at a path under the project's own hostname. Securing MCP credentials and identity is covered in Secure MCP secrets and identity.

Step 3: Confirm profile isolation​

The profile inherits the project's isolation.

  • It is reachable only through the project's gateway hostname. Called on another project's gateway, the path is not served and returns 404.
  • It accepts only the project's keys. A key from another project is refused with 403.

The developer-side workflow of connecting a client such as Claude Code, Cursor, or an MCP-capable editor to the profile URL is covered in Aggregate MCP servers into a profile.

What to do next​

Where to go next

Govern MCP server access

The organisation-wide catalog and controls behind per-project grants.

Aggregate MCP servers into a profile

The developer-side view of connecting a client to a profile.