> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/gong.md). # Gong Create a Gong MCP server integration and paste its credentials into Cakewalk so agents access Gong through the gateway. Connect your company's Gong instance to Cakewalk's MCP Gateway. Every agent tool call against Gong passes through the gateway and is evaluated against your Policies. Gong hosts its own MCP server. Cakewalk routes to it, so setup is one integration created inside Gong, plus a Client ID and Client secret pasted into Cakewalk. ## Requirements * Tech admin role in Gong. * A paid Gong seat. * Enough Gong credits to query the MCP server. ## Required Scopes Gong's MCP server publishes two scopes, `mcp:read` and `mcp:write`. Cakewalk requests them during the OAuth flow, so there is no scope list to select in Gong. ## Step 1: Open the MCP Servers Tab 1. Open Gong as a Tech admin. 2. In the left sidebar, go to **Admin center**. 3. Open the **Settings** tab. 4. Under **Ecosystem**, click **MCP**. 5. Open the **MCP servers** tab. {% hint style="info" %} Gong has a second integration surface under **Ecosystem** > **API**, for apps built on Gong's REST API. That one asks for granular `api:*` scopes and does not connect to the MCP server. Create the integration on the **MCP servers** tab. {% endhint %} ## Step 2: Create the Integration 1. Click **New MCP server integration**. 2. In **Integration name**, enter a name your admins will recognize, for example `Cakewalk`. 3. In **Redirect URI**, paste this URL on its own line: ``` https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback ``` Gong takes one URL per line. Cakewalk needs only this one. ## Step 3: Set the Registration Type Choose **Manual**. Gong then issues a Client ID and a Client Secret, which is what Cakewalk's Gong Connection expects. **Automatic** issues no credentials and lets any matching client connect. Cakewalk's Gong Connection is configured for a Client ID and secret, so an Automatic integration leaves it with nothing to authenticate with. ## Step 4: Set the Authorization Context This sets how much Gong data an agent can access. * **Personal access**, Gong's default: the agent accesses only the data of the employee who authorized the Connection. * **Shared access**: the agent accesses all of your company's Gong data. Choose **Personal access** unless your company's agents need Gong data beyond the authorizing employee's own. Personal access keeps every agent inside the Gong access its employee already holds. ## Step 5: Save and Copy the Credentials 1. Click **Save**. 2. Gong shows the **Client ID**, the **Client Secret** and the **Server URL**. Use the **Copy** button next to the Client ID and the Client Secret. 3. Click **Done**. Copy both values before you click Done. You do not need the Server URL. Cakewalk already routes to Gong's MCP server. ## Step 6: Paste Credentials Into Cakewalk 1. Open . 2. Go to All Connections. 3. Find Gong. 4. Click Edit credentials. 5. Paste the values into **Client ID** and **Client secret**. 6. Save. ## Verifying It Works The Gong Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to summarize a recent Gong call. If Gong returns content, the Connection is live. ## Troubleshooting * Invalid redirect URI on consent: the **Redirect URI** on the Gong integration must match `https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback` exactly, with no trailing slash. * No credentials to paste into Cakewalk: the integration was created with **Registration type** set to **Automatic**. Create it again with **Manual**. * The agent returns nothing for calls other employees own: the integration is set to **Personal access**. Switch **Authorization context** to **Shared access** if agents are meant to access data across your company's whole Gong workspace. * Queries stop returning content: Gong requires enough credits to query the MCP server. Check your company's Gong credit balance before treating this as a Connection problem. ## Learn More * [Create an integration to connect to the MCP server](https://help.gong.io/docs/create-an-integration-to-connect-to-the-mcp-server) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/gong.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.