Skip to main content
MCP (Model Context Protocol) is how services expose purpose-built tools directly to agents. When a service publishes an MCP server, connecting it gives your agent a set of tools designed for agent use, not just access to a REST API. One-click, via the catalog: Many MCP servers use OAuth with dynamic client registration, which means no manual setup. Click the service in the catalog, authorize with your account, and the agent is connected. The credential is stored securely and attached to every request automatically. By URL, for any MCP server: You can connect any MCP server directly by pointing the agent at its URL.
Or add it directly in the agent’s tools settings. The agent handles the rest. Authenticated MCP servers: When an MCP server requires authorization, a connect card appears. Authorize once. The proxy attaches the credential to every future request automatically. The token never appears in the agent’s prompts.
An MCP connect card grants access at whatever level that server’s OAuth app requests, which is often the full workspace or account. This is different from some OAuth flows (like Notion’s) where you pick individual pages. On MCP Connect you won’t see an item picker.

​
What MCP adds over an API

An API gives the agent endpoints. An MCP server gives it tools with descriptions, typed arguments, and semantics written for an agent to read. The agent spends less effort working out how to call the service and more on the actual job.

​
Managing a connection

Once a service is connected, manage it from the integration’s card in your workspace. The card shows which agents use the connection and gives you two options to pull access back:
  • Remove from one agent. The connection stays live for your other agents.
  • Disconnect entirely. This revokes Skydive’s access at the provider and removes it from every agent using it.

Catalog

Every service available to connect.

Permissions

How credentials stay out of the model’s reach.