Agent Connections
The catalog of third-party apps your Agents access through the MCP Gateway, and how much setup each connection needs.
Last updated
Was this helpful?
The catalog of third-party apps your Agents access through the MCP Gateway, and how much setup each connection needs.
Agent Connections are the downstream apps an Agent accesses through Cakewalk's MCP Gateway: collaboration, dev tools, observability, sales, support, finance and more. Admins curate which ones appear in their organization. How much setup each one needs depends on the app, from a single sign-in to registering an OAuth app.
Agent Connection: A third-party app an agent can call (Slack, GitHub, Jira, Linear and so on).
Setup flow: How a connection gets authorized. There are three: sign in and go, register your own app, or allowlist Cakewalk's app.
💡 Why this matters: The catalog defines what your Agents can access. A connection's setup flow tells an Admin up front whether enabling it is one click or a short OAuth setup.
What an Admin does to enable a connection depends on how the app handles OAuth. Every Connection in the catalog falls into one of three flows.
The app registers with Cakewalk automatically (Dynamic Client Registration), or Cakewalk already ships the OAuth app. The Admin enables the Connection, the employee signs in, and that is it. No credentials to manage.
The app does not register automatically. Before employees can connect, an Admin creates an OAuth app in the vendor's console, points its redirect URL at Cakewalk, and pastes the Client ID and Secret into Cakewalk. The per-connection page lists the exact steps and scopes.
Used mainly for Google Workspace and Microsoft services. Cakewalk publishes a Client ID and the Admin allowlists it in the vendor's admin console. No app to build, no secret to paste.
Most apps map to a single MCP server. Some map to several, and a few are bundled:
Regional or sub-product variants appear as separate Connections so Admins enable exactly the surface they want (for example, Amplitude US and Amplitude EU).
Bundles group a suite's MCP servers into one Connection. Microsoft 365 and Google Workspace are bundled, so an Admin enables the suite once and employees get every sub-app under it.
Admins populate the catalog two ways: a direct Google Workspace sync that imports everything it discovers, or a manual pick from the full catalog (the same picker used for Agent Platforms). After setup, they manage it from All Connections.
For the step-by-step, see Admin Setup.
Agent Platforms: the runtimes that originate tool calls, and how they connect
The Three Actors: User → Agent → Connection
All Connections: admin curation surface
My Connections: the employee self-service surface
Last updated
Was this helpful?
Was this helpful?