# Agent Connections 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. ### 📖 Key Concepts * **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. :bulb: *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. *** ### 🔐 The Three Setup Flows 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. #### Sign in and go 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. #### Register your own app 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. #### Allowlist Cakewalk's app 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. *** ### 🧩 Why a Vendor Appears More Than Once 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. *** ### 🛠 How Connections Get Into Your Catalog 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](/docs/ai-agent-access/how-to-guides/connections/all-connections.md). For the step-by-step, see [Admin Setup](/docs/ai-agent-access/introduction/get-going-with-agent-access/admin-setup.md). *** ### 📚 Related * [Agent Platforms](/docs/ai-agent-access/connections-and-integrations/agent-platforms.md): the runtimes that originate tool calls, and how they connect * [The Three Actors](/docs/ai-agent-access/concepts/the-three-actors.md): User → Agent → Connection * [Connection and Agent Statuses](/docs/ai-agent-access/concepts/connection-and-agent-statuses.md) * [All Connections](/docs/ai-agent-access/how-to-guides/connections/all-connections.md): admin curation surface * [My Connections](/docs/ai-agent-access/how-to-guides/connections/my-connections.md): the employee self-service surface --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.