Connect its tools

Import tools from an MCP server

Bring an MCP tool surface into the same catalog, identity, and audit controls as other integrations.

Captured from the product Demo workspace

Import a live MCP server as a governed integration and re-sync it later.

What this changes for your team.

Enter an MCP server URL to import its tools and review what they can do. Sync again when the provider changes its tools, then review the updates.

01
Configure the MCP server endpoint and the credential needed to inspect it.
02
Import the server's tool schemas into a governed integration revision.
03
Re-sync deliberately when the remote server changes, then review the resulting revision.

What to expect, including limits that matter to your team.

Agents use the saved version of imported tools until you update it.

MCP credentials follow the same encrypted connection model used by other integrations.

Remote tool changes require a re-sync before they enter the governed local catalog.

Complete the operating path

Apply approval and governance rules from an explicit effect classification.

Give agents controlled access to internal or niche APIs without waiting for a shipped connector.

Make every integration call act as a deliberate team, user, platform, or customer identity.

Bring one real process

Start with a job your team already owns, plus the tools and decisions around it.