Integrations

Accounts vs MCP

The two integration models compared: connected accounts for standard SaaS APIs, and remote MCP servers for custom tool servers.

Connected accounts

Connected accounts cover well-known SaaS APIs: Gmail, Slack, GitHub, Salesforce, and 45 providers in all. Authenticate once through an OAuth consent flow; the account provider (Composio or Nango) stores the credentials, and agents call the service's HTTP API through the secure proxy, which injects the token outside the container. Access is controlled per OAuth scope with scope policies, and every call is audited.

Best for: standard SaaS integrations with managed OAuth and scope-level access control.

Remote MCP servers

Remote MCP servers expose discrete, named tools over the Model Context Protocol, an open standard for tool servers over HTTP. The agent calls search_contacts or create_issue, not POST /api/v2/contacts. Register any server by URL with a bearer token, OAuth, or no auth; Gamut discovers its tools and proxies calls with the same token isolation, governed by per-tool MCP tool policies. See Remote MCP Servers.

Best for: custom internal services, specialized capabilities, or any tool server that speaks MCP.

Comparison

Connected accountsRemote MCP servers
Integration modelRaw HTTP API calls via proxyNamed tools via JSON-RPC
Auth managementManaged OAuth (Composio or Nango)Bearer token or OAuth (including PKCE)
Policy granularityPer scope (gmail.readonly)Per tool (search_contacts)
Provider support45 built-in SaaS providersAny MCP-compatible server
SetupOne-click OAuth consentRegister URL and credentials
Best forGmail, Slack, GitHub, SalesforceCustom tools, internal APIs

Using both together

The two models combine freely. An agent can read and send email through a connected Gmail account while calling search_knowledge_base on a company MCP server. Both types are mapped to agents individually, so each agent sees only the integrations assigned to it. See Mapping Accounts to Agents.