G2 MCP Server

The G2 MCP server is a remote, provider-hosted Model Context Protocol server maintained by G2. It brings G2's first-party buyer intent data, competitive intelligence, product catalog, and review analytics into AI assistants so agents can ground their answers in verified G2 marketplace data rather than scraped web content. G2 launched the integration in Q1 2026, with Claude as the first supported AI assistant. A companion HubSpot integration via Breeze Agents was released in April 2026.

The server is read-only and is designed for go-to-market teams. It lets an AI agent retrieve recent buyer intent activity for specific companies, identify which competitors a prospect is researching, rank accounts by intent score and engagement level, summarize signal types (profile views, comparison pages, pricing views), and surface review-based insights about products and categories. Intent scores are returned on a 0 to 100 scale alongside firmographic context such as company size, location, and domain.

Authentication is handled through OAuth: when you connect the server, the client opens a browser window to sign in with the G2 account associated with your seat. Access to buyer intent data typically requires a G2 Buyer Intent subscription. Because it is a hosted remote server, there is no code to clone or run locally. You add it as a custom connector by URL in Claude or another MCP-compatible client.

Tools

The G2 MCP server is hosted by G2. There is nothing to install locally. You connect to it as a remote MCP connector using OAuth.

Prerequisites

• A G2 account with access to the data products you want to query (Buyer Intent typically requires a paid G2 subscription).
• An MCP-compatible client such as Claude (web, Desktop, mobile, Claude Code, or the API).
• Sign in to your AI client with the same email address used on your G2 account.

Connect in Claude (web or Desktop)

• Click the + icon below the chat box.
• Select Connectors > Manage Connectors.
• Find and add the G2 connector (listed at https://claude.com/connectors/g2), or add it as a custom connector using the remote MCP server URL provided in the G2 documentation.
• Claude opens a browser window. Sign in to G2 and authorize access.

Generic remote MCP client config

For MCP clients that take a JSON connector configuration, the entry follows the standard remote MCP pattern. Replace <G2_MCP_URL> with the URL listed in G2's official documentation:

{
  "mcpServers": {
    "g2": {
      "url": "<G2_MCP_URL>",
      "transport": "http"
    }
  }
}

The exact server URL is provided by G2 on the documentation page and through Claude's connector directory. See https://documentation.g2.com/docs/g2-mcp-server for the current endpoint and the latest setup instructions.

• Generate a pre-call briefing for a target account that combines G2 intent score, competitors being evaluated, and recent activity timeline.
• Prioritize SDR outreach by pulling the top accounts researching your product this week, ranked by intent score and visitor count.
• Detect churn risk by surfacing existing customers showing intent activity on competitor profiles in your category.
• Inform competitive positioning by querying review sentiment and most-mentioned strengths for your product versus named competitors.
• Enrich CRM workflows so an agent can pull G2 buyer intent context when a deal stage changes or a new contact is created.

• "Give me a pre-call briefing for Confluent using G2 data."
• "Show me companies researching our product this week with their intent scores and which competitors they're comparing."
• "Which accounts in my pipeline have the highest G2 intent score in the last 14 days?"
• "Summarize recent G2 reviews about Snowflake in the data warehouse category and list the most mentioned strengths."
• "Are any of our current customers showing intent activity on competitor profiles right now?"

• Official, provider-hosted server maintained by G2, so data freshness and auth are managed for you.
• Read-only OAuth flow means no API keys to manage and access scopes match your G2 seat permissions.
• Available across the full Claude surface (web, Desktop, mobile, Claude Code, API) and through HubSpot Breeze Agents.
• First-party intent and review data is more trustworthy for GTM decisions than scraped or inferred signals.

• Read-only: the server cannot write back to G2 or update records.
• Most useful capabilities depend on a paid G2 Buyer Intent subscription tied to your account.
• Public documentation does not enumerate exact tool names or parameter schemas, so tool-level behavior must be discovered at runtime.

• 6sense or Bombora MCP-compatible integrations for third-party intent data (where available).
• Clearbit or Apollo MCP servers for firmographic enrichment, though they lack G2's review and comparison signal data.
• HubSpot MCP server combined with the G2 HubSpot integration for teams that want intent data routed through their CRM.