Secure G2 access for AI agents
Browse G2's product, vendor, and category catalog, analyze buyer intent and competitive intelligence, read reviews, and manage research boards, using G2's official MCP server.
G2 connects your agents to product, vendor, and category data, buyer intent and competitive intelligence, reviews, and research boards – useful for sales and market research workflows, but also a window into what your prospects and competitors are doing. Every call runs through your policies and is logged for audit.
Server URL: https://mcp.g2.com/mcp
Credential modes
G2 supports bring your own app only. It does not support dynamic client registration for this MCP server, so your organization registers its own OAuth app in G2 and supplies the client ID and secret. See Credential modes for how the modes compare.
Before you begin
- A G2 account that can create OAuth apps in G2's developer portal, plus a G2 subscription covering the data your agents need.
- Administrator access to your Agent Authority workspace, to add the resource.
Setup moves between two consoles. You copy a redirect URI in the Agent Authority console, register an OAuth app in G2, then return to the console and paste the credentials. Keep both tabs open as you work.
Setup
1. Copy the redirect URI
In the Agent Authority console, go to Resources → Add Resource and select G2. G2 is bring-your-own-app only, so the credentials form opens as soon as you select it, with no mode to pick.
Copy the Redirect URI shown on the form. It includes your tenant's region, so copy it rather than typing it. It takes the form https://oauth.aisecurity.services.<region>.connect.secureauth.com/auth/callback.
Leave this page open. You come back to it in step 3.
2. Register an OAuth app in G2
Go to my.g2.com/developers and sign in, then open OAuth Apps and click + New OAuth App.
- Fill in the Name, Privacy Policy URL, and Terms of Service URL. Your users see the Name on G2's authorization screen, so choose one they will recognize.
- Under Redirect URLs, paste the Redirect URI from the form in the Agent Authority console, using the Copy button next to it.
- Select the Confidential checkbox. The gateway always sends a client secret, so the app has to be a confidential client.
- Select the permissions listed under Required scopes, or select All.
Click Save, then copy the Client ID and Secret from the App Details page.
3. Finish in the console
Back on the G2 form in the Agent Authority console, paste the Client ID and Client Secret.
Set Token Endpoint Authentication to Client secret in POST body. G2 advertises support for both client_secret_basic and client_secret_post, so leaving this on Auto-detect can settle on the wrong one and fail the token exchange. Then click Add.
The gateway sends you to G2 to sign in, through your SSO if configured, and authorize the app. Review the requested access and click Allow Access. You return to the console with your G2 account connected.
Verify the connection
The gateway syncs the G2 tools automatically. To check the connection end to end, ask your agent to run a request:
List G2 categoriesIf G2's category list comes back, the connection is working.
How users connect
Access is per user. Each additional user connects their own G2 account the first time their agent calls a G2 tool: the gateway returns a sign-in link, the user authorizes once, and the tools work from then on. Go to Connections to manage linked accounts.
G2's own account and subscription-level permissions control what each user can reach. The gateway does not widen access beyond what the authenticated user could already do in G2.
Available tools
| Tool | Description |
|---|---|
list_categories / show_category | Browse G2's category taxonomy, or get details for one category |
list_products / list_my_products / show_product | Browse the product catalog, list products owned by the current account, or get one product's details |
list_vendors / show_vendor | Browse the vendor directory, or get one vendor's details |
list_standard_product_reviews | Get standard reviews for a product |
list_market_intelligence_product_reviews | Get reviews with B2B company context, for competitive/market analysis |
browse_buyer_intent / browse_product_buyer_intent | Analyze buyer intent interactions across products, or for a single product |
show_buyer_intent_dashboard | Display an interactive buyer intent dashboard for a product |
browse_competitive_intelligence | Analyze which competitors prospects are evaluating |
list_research_boards / show_research_board / list_research_board_products | List research boards, show one board, or list its products |
create_research_board / update_research_board / delete_research_board | Create, rename, or delete a research board |
add_products_to_research_board / remove_products_from_research_board | Add or remove products on a research board |
show_upgrade_widget | Display G2's plan upgrade widget when a tool hits an access restriction |
Required scopes
Select these permissions when you register the app. The gateway requests exactly this list when a user authorizes, so a permission the app is missing stops the tools that depend on it.
openid,profile– identify the signed-in user.products.read– read product catalog data.products.reviews.read– read product reviews.vendors.read– read vendor directory data.buyer_intent.read– read buyer intent and competitive intelligence data.research_boards.read,research_boards.write– read and manage research boards.
Policy examples
- Read-only access: deny
create_research_board,update_research_board,delete_research_board,add_products_to_research_board, andremove_products_from_research_board - Catalog browsing only: allow
list_categories,show_category,list_products,show_product,list_vendors,show_vendor - Keep buyer intent and competitive data out of an agent's reach: deny
browse_buyer_intent,browse_product_buyer_intent,show_buyer_intent_dashboard,browse_competitive_intelligence
Next steps
- Create a policy – start from the read-only pattern in Policy examples above.
- Connections – manage the G2 accounts your users have linked.