Version 3.0
Administration
Connections
MCP servers

MCP servers

Model Context Protocol servers extend the platform with new tools and resources, governed centrally and mountable into Projects. The /mcp page in the product has two tabs: Catalog (pre-built templates the platform ships) and Connected (servers your workspace has installed).

Audience: IT (the enabler), workspace admins, and team admins

Who can manage MCP

Only workspace admins or the current active team's admin can install, edit, or remove MCP servers. Builders without those roles see the page but cannot manage it.

Two install paths from the Catalog

Each Catalog template has one of two primary actions, decided by the platform based on whether the server needs setup beyond what the catalog row provides.

  • Install. Direct install. The catalog entry has everything the platform needs (endpoint, auth defaults). One click connects it.
  • Set up. Configuration is needed. Click and the install dialog opens prefilled with the catalog defaults; you complete the setup (such as providing a bearer token or completing OAuth).

The dialog title reflects which path you are on: Install or Set up <server name>.

Add a server that is not in the Catalog

Use Add server to register a custom MCP server by URL. The dialog title is "Add server".

Open Add server

The Add server action is on the MCP page. The composer opens with empty fields.

Fill in the server details

The required fields are Display name (placeholder example: "GitHub"), Remote URL (the MCP endpoint, for example https://example.com/mcp), and an optional Description.

Pick the authentication mode

Three modes are supported:

  • No auth. The server is public or runs without authentication.
  • Bearer token. A shared token the server expects in the Authorization header. You paste the token; the platform stores it.
  • OAuth. Per-user OAuth flow. After install, each user who wants to use the server authorizes once.

Save

Click Add server. The server appears in the Connected tab.

The Connected tab

Once installed, servers show in the Connected tab with three filters across the top: Status (all, ready, needs setup, off), Authentication (all, user OAuth, Bearer token, no auth), and Scope (all, workspace, team).

Each row exposes a Mounting toggle that is independent of connection state. A server can be installed but its mounting can be off (for testing or temporary disablement) without removing the credential.

Status is not the same as Mounting. "Ready" means the server is configured and reachable. "Needs setup" means a credential or OAuth step is still pending. "Off" means the mounting toggle is off, regardless of credential state. A server can be Ready but Mounted off, and that is a valid intentional state.

Scope: workspace or team

A server can be installed for the whole workspace or scoped to the active team. The Scope filter lets you see one slice or the other. Team admins manage team-scoped servers; workspace admins can manage either.

What this article will cover

  • Browsing the Catalog
  • Installing a direct-install catalog server
  • Setting up a catalog server that needs configuration
  • Adding a custom MCP server (Display name, Remote URL, Description)
  • Choosing No auth, Bearer token, or OAuth
  • Workspace versus team scope
  • The Mounting toggle and what it does
  • Filters on the Connected tab (Status, Authentication, Scope)
  • How builders mount a server inside a Project
ExaData sources