Gong
Gong's official MCP server answers questions about accounts and deals using Gong's AI. The server is hosted by Gong at https://mcp.gong.io/mcp and uses OAuth. It is not in the Willow catalog, so you add it as a custom MCP server.
Willow also has a built-in Gong connector, which calls Gong's REST API.
Official server or built-in connector
The two expose different tools.
| Official MCP server | Built-in connector | |
|---|---|---|
| Tools | ask_account, ask_deal, generate_brief | list-calls, get-call-details, get-call-transcripts, get-detailed-calls, list-users |
| Returns | Answers and briefs generated from calls, emails, and CRM data | Call lists, call details, transcripts, and users |
| Call transcripts | Not returned | Returned |
| Gong identity | Each user's own Gong account, with Personal access | One shared API key, or each user with OAuth |
| Gong cost | Gong credits per request | Gong API rate limits |
Use the official server for questions and briefs, such as the open risks on a deal. Use the built-in connector when an agent needs the records themselves, such as last week's calls or a full transcript. You can add both.
Who can use it
With the built-in connector on API Key, every tool call uses one API key created by a Gong admin. Every user has the same access, and Gong attributes the calls to the key.
With the official server on Personal access, each user signs in with their own Gong account. The agent sees only what that user can see in Gong. Users do not need an API key, so anyone with a paid Gong seat can connect.
Before you start
You will need:
- A paid Gong seat for every user who connects. Gong Collaborator seats cannot use the MCP server.
- Enough Gong credits. Each request to the server consumes credits, the same amount as the equivalent Gong API request. When credits run out, requests return an error.
- A Gong tech admin to create the MCP server integration in Gong.
See Create an integration to connect to the MCP server in Gong's documentation.
Set up Gong
A Gong tech admin creates one integration for the company.
1. Create the integration
In Gong, go to Admin center → Settings → Ecosystem → MCP → MCP servers and click New MCP server integration. Enter an Integration name, such as Willow.
2. Add the redirect URI
In Redirect URI, enter your Willow callback URL:
- For SaaS deployments:
https://{org}.mcp-s.com/{org}/api/auth/callback - For On-Premise deployments:
{connectUrl}/{org}/api/auth/callback
Willow shows the exact URL on the server's Setup tab, under Client ID & secret. Copy it from there. Gong requires an exact match.
3. Choose the registration type
- Automatic: Gong does not issue a client ID or secret. Willow registers a client, and Gong accepts it because the redirect URI matches.
- Manual: Gong issues a Client ID and Client Secret after you save. Copy both for Willow.
4. Choose the authorization context
- Personal access (default): The agent can access only the data of the user who authorized it.
- Shared access: The agent can access all of your company's Gong data.
Use Personal access unless every user who can connect in Willow should see all Gong data. If you use Shared access, limit access to the server with Willow groups.
Gong does not let you change the registration type or authorization context after you save. To change either one, delete the integration and create a new one. Deleting revokes every token issued through it, so users must connect again.
5. Save the integration
Click Save. For Manual registration, copy the Client ID and Client Secret.
Set up Willow
1. Add the server
- Go to MCP Servers → + Add MCP Server and click Configure on the Custom MCP card.
- Enter a Name, such as
Gong. - Set Server URL to
https://mcp.gong.io/mcp. Leave Transport on HTTP / SSE. - Click Create Integration.
Willow detects that Gong uses OAuth and sets the server to Proxy OAuth.
2. Match the registration type
On the Setup tab, choose the option that matches Gong:
- Automatic in Gong: Select Automatic (discovery). Willow registers the client. If you created the Gong integration after adding the server, click Discover OAuth Settings.
- Manual in Gong: Select Client ID & secret and paste the Client ID and Client Secret from Gong.
See Configure Proxy OAuth for the other options.
3. Test and publish
- Click Check connection and sign in to Gong.
- Sync the tools. You should see
ask_account,ask_deal, andgenerate_brief. - Assign groups and click Publish.
Each user signs in with their own Gong account the first time they use the server.
Tools
| Tool | Description |
|---|---|
ask_account | Answers a natural-language question about one account. |
ask_deal | Answers a natural-language question about one CRM deal. |
generate_brief | Generates a structured summary of an account, deal, or contact. |
The server is read-only. It does not return call transcripts, email bodies, or activity lists, and it excludes private calls. See About the Gong MCP server.
Each request consumes credits. Shorter date ranges and specific questions use fewer. See Gong's guide to credit consumption.
Troubleshooting
Gong says the tool is not authorized for the company
Cause: No Gong integration matches the client Willow registered.
Solution: Confirm that a tech admin created the integration and that its Redirect URI matches Willow's exactly. For Manual registration, use Client ID & secret in Willow, not Automatic (discovery).
A user cannot connect
Cause: The user has a Gong Collaborator seat.
Solution: Assign the user a paid Gong seat.
Tool calls return errors after working
Cause: The company has used up its Gong credits.
Solution: Check the credit balance in Gong.
A known call is missing from answers
Cause: The call is private, or the user who connected cannot access it in Gong.
Solution: Check the call's privacy and the user's permissions in Gong.
Built-in connector tool calls return 404
Cause: The built-in connector's Base URL is set to https://mcp.gong.io/mcp.
Solution: See the built-in connector's troubleshooting.