Set up Gong
Make Gong calls and transcripts searchable in Glean, and optionally connect Gong's Model Context Protocol (MCP) tools. Use this guide when your setup page shows Set up indexing, Connect MCP, and Review setup.
Indexing and MCP use separate authorization. Complete indexing authorization first, even if you plan to defer the crawl.
The two connections provide different capabilities:
| Capability | Authorization | Availability |
|---|---|---|
| Indexed search | Authorize Glean's indexing integration with a Gong account that has the required permissions. | Search content after Glean indexes it, subject to connector access and the permissions Glean indexes from Gong. |
| Gong MCP tools | Register an MCP integration in Gong, then authorize each user's Gong account. | Use tools after MCP connects and Glean discovers them, subject to tool access and the user's Gong permissions. |
Prerequisites
Before you begin, complete the following prerequisites:
- Have permission to add connectors in Glean.
- Use Gong's cloud service and allow Glean to access the Gong API over the internet.
- Have a Gong admin account, or an account with permission to read users, permission profiles, workspaces, library folders, calls, transcripts, and metadata.
- If you plan to connect MCP, have a Gong Tech admin available to register the integration. Each person who uses Gong MCP needs a paid Gong seat, and tool requests consume Gong credits. Collaborator accounts can't use Gong MCP.
Set up indexing
Authorize the integration Glean uses to crawl Gong content and permissions:
- In the Glean Admin console, go to Connectors, click Add connector, and choose Gong.
- In Set up indexing, enter a connector name in Name.
- Click Connect.
- Sign in to Gong with the account you prepared and approve the authorization request.
- Return to Glean and continue to Connect MCP after authorization succeeds.
This authorization covers indexing. It does not connect Gong MCP tools.
(Optional) Connect MCP
To use indexing without MCP, click Skip and continue to Review setup. You can connect MCP later through the connector's Edit setup flow.
To connect MCP, choose a registration method. Automatic registration is selected by default. It still requires a Gong Tech admin to register the integration and add the redirect URL in Gong.
- Automatic registration
- Custom app
Use automatic registration when you don't need to manage a custom OAuth client ID and secret:
- In Glean, leave Automatic registration selected and copy the Redirect URL.
- In Gong, have a Tech admin go to Admin center → Settings → Ecosystem → MCP → MCP servers.
- Click New MCP server integration and enter a name, such as
Glean, in Integration name. - Paste the URL from Glean into Redirect URI. It must match the URL Glean displays exactly.
- Set Registration type to Automatic and Authorization context to Personal access.
- Under Advanced settings → Authorization scopes, keep Read and Write enabled, then click Save.
- Return to Glean, click Connect, and sign in to Gong to approve access. Glean registers the OAuth client automatically.
Use a custom app when you need to supply your own MCP client credentials:
- In Glean, click Set up a custom app instead and copy the Redirect URL.
- In Gong, have a Tech admin go to Admin center → Settings → Ecosystem → MCP → MCP servers.
- Click New MCP server integration and enter a name, such as
Glean, in Integration name. - Paste the URL from Glean into Redirect URI. It must match the URL Glean displays exactly.
- Set Registration type to Manual and Authorization context to Personal access.
- Under Advanced settings → Authorization scopes, keep Read and Write enabled, then click Save.
- Copy the MCP integration's client ID and client secret into Client ID and Client secret in Glean. Don't use indexing credentials.
- Click Connect, then sign in to Gong and approve access.
With Personal access, Gong limits each user's tool requests to that user's permissions. After authorization succeeds, wait for Glean to discover the tools before continuing to Review setup. Closing the sign-in window or failing authorization does not complete the MCP step.
These instructions use Gong's standard admin experience. Gong partner accounts use a different setup page. See Create an integration to connect to the MCP server for Gong's requirements and partner-account guidance.
Review setup
Review the connection status and choose when to start indexing:
- Confirm that indexing authorization succeeded. Check that MCP connected successfully if you chose to configure it.
- If User access appears, choose All users, Test group only, or None. If you choose Test group only, select the test group.
- Click Begin indexing to start the initial crawl.
If Skip for now appears on this step, it defers the crawl. It is separate from Skip on Connect MCP, which skips the optional tools connection.
Selecting All users does not override the Gong permissions Glean maps for indexed content. See Gong overview for indexing and permission limitations.
Manage tools and verify setup
After setup, open the connector's Tools tab to review the available tools and their access settings. Each user authorizes their own Gong account before using MCP tools.
Verify the connections separately:
- After the initial crawl, search for a known Gong call or transcript and confirm that the expected users can find it.
- Check permissions with users who have different access in Gong. Confirm that search results reflect the connector's supported permission mappings.
- If you connected MCP, run a Gong tool with an authorized user and confirm that it returns the expected result. A successful indexing connection does not prove that MCP works.
Troubleshoot setup
Use the symptom to identify which connection needs attention:
| Symptom | What to check |
|---|---|
| Indexing authorization fails. | Check the Gong account's permissions, then retry Connect in Set up indexing. |
| MCP authorization fails or the step remains incomplete. | Check that the redirect URI matches Glean, the registration method matches your selection, and the user has a paid Gong seat. Complete authorization, or click Skip to proceed without MCP. |
| Client ID or Client secret is missing for a custom app. | Copy both credentials from the Gong MCP integration. Indexing authorization does not supply them. |
| No tools synced yet appears after you skipped MCP. | This is expected for indexing-only setup. Use Edit setup to connect MCP when you need tools. |
| Gong reports insufficient credits. | Ask your Gong admin to check the available Gong credits. Gong MCP tool requests consume Gong credits. |