Vendor-specific MCP requirements
Some remote MCP servers require vendor-specific token headers, OAuth settings, or additional request metadata. Review Connect remote MCP servers to Glean before you set up these servers.
Refer to the Custom HTTP headers page for general header behavior. Use this page to review validated vendor-specific requirements and examples.
For further assistance, contact Glean Support.
Vendor-specific token requirements
Some remote MCP servers share tools with Glean only when you connect with a token that contains the correct vendor license. Without this license, the connection succeeds, but Glean receives no tools to display.
ZoomInfo
To connect to [https://mcp.zoominfo.com/mcp](https://mcp.zoominfo.com/mcp), assign a ZoomInfo Copilot license or a ZoomInfo Copilot Bundle product to the user who creates the ZoomInfo developer or OAuth token. An admin-only ZoomInfo license does not provide access.
Without one of these licenses, Glean connects to the server, but ZoomInfo rejects the request to list tools. As a result, no ZoomInfo tools appear in the Glean tools list, and you cannot add them to agents. If no tools appear after you connect the server, verify the license assigned to the user who created the token.
Vendor-specific OAuth application requirements
Some remote MCP servers require you to configure the OAuth application for production before other users can authorize access.
Airtable
If the connection works only for the admin who created it, update your application settings in Airtable:
- Open Builder Hub > Integrations > OAuth integrations.
- Locate the Support information section.
- Enter the email address of the OAuth application owner in the Support email field.
- Add the privacy policy URL and terms of service URL of the application owner into the corresponding fields:
- Glean-owned applications: Use
[https://www.glean.com/privacy](https://www.glean.com/privacy)for the privacy policy URL and[https://www.glean.com/legal/terms](https://www.glean.com/legal/terms)for the terms of service URL.
- Glean-owned applications: Use
- Select Save changes.
- Ask the other users to retry the connection.
If Airtable still restricts the application to development use, other users might receive an access_denied error even when the redirect URI, scopes, and credentials match the required settings.
Custom headers
Configure header values and authentication settings for specific remote MCP servers in this section.
Marketo MCP
Authentication requirements
- MCP endpoint:
[https://marketo-mcp.adobe.io/mcp](https://marketo-mcp.adobe.io/mcp) - Glean authentication method: API Key
- OAuth authorization URL: Not required for this configuration
- Required vendor values:
- Marketo Client ID
- Marketo Client Secret
- Munchkin ID