Gongio MCP vs Search Console MCP
A side-by-side look at the Gongio MCP and Search Console MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gongio MCP for customer data platforms work as a local process; choose Search Console MCP for customer data platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gongio MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GONG_ACCESS_KEY, GONG_ACCESS_KEY_SECRET. - You want tools like
list_calls, get_call_summary, get_call_transcript.
Choose Search Console MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- Its auth model fits you: OAuth 2.0.
- You want tools like
get_started, sites_list, sites_manage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 64/100 · Good | 65/100 · Great |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | GONG_ACCESS_KEYGONG_ACCESS_KEY_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 22 | 306 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 15 | 25 |
| Full listing | View Gongio MCP | View Search Console MCP |
Tools & capabilities
Gongio MCP tools 15
list_callsList Gong calls with optional date filtering. Returns minimal call metadata (ID, title, date, duration). Use get_call_summary for details or get_call_transcript for full transcript.get_call_summaryGet an AI-generated summary of a single call including brief overview, key points, topics, action items, and detailed outline. This is the recommended way to understand a call - use get_call_transcript only if you need exact quotes.get_call_transcriptGet the raw transcript for a single call with speaker-attributed text. Only use this when you need exact quotes - prefer get_call_summary for understanding call content. Transcripts are truncated by default (10KB) to prevent context overflow - use maxLength and offset to paginate.list_usersList all Gong users in the organization. Returns name, email, title, and user IDs. Useful when you need a Gong user ID for search_calls filters like primaryUserIds, though for most "find calls by this person" cases you can pass their email directly to primaryUserEmails or participantEmails instead.search_callsSearch Gong calls with rich filters. The primary tool for narrowing down calls before drilling in with get_call_summary or get_call_transcript. Supported filters: - When: fromDateTime, toDateTime (ISO 8601). Always prefer a date range — unbounded queries pull every call in the workspace. - Who hosted: primaryUserIds, primaryUserEmails, excludePrimaryUserIds. - Who participated (host OR attendee OR invitee): participantUserIds, participantEmails, excludeParticipantUserIds, excludeParticipantEmails. - Customer/topic: customerName (CRM account name, email domain, or title substring), titleContains, trackers (see note below). - Metadata: scope (External/Internal), direction, system (Zoom/Meet/…), language (eng/jpn/…), minDuration and maxDuration in seconds. - Output shape: include (array of keyPoints, trackers, highlights, speakers, comments, context, outline, media). Parties + brief + topics are always returned. Behavior: - Auto-paginates up to ~5000 calls. If a user asks for a broad question, guide them to narrow with a date range, scope, minDuration, or customerName first. - trackers filter does case-insensitive substring match on tracker names. Names are workspace-specific — call get_trackers first to see what's configured before guessing. - When the rich output would exceed the output cap, the tool auto-falls back to a compact table showing all IDs/titles. Use get_call_summary on specific IDs to go deeper. - Filters compose with AND logic (primaryUserIds + customerName = hosted by user X on customer Y calls). Usage pattern: narrow with search_calls → drill into specific calls with get_call_summary (AI summary) or get_call_transcript (exact quotes).search_calls_by_accountFind calls involving a specific account/company by matching email domains of external participants. The Gong API does not natively support filtering by account name — this tool fetches calls in the date range and post-filters on parties[].emailAddress. Auto-paginates up to maxCalls. For external tech-stack joins (e.g., "all calls with prospects on Klaviyo"), resolve domains upstream and pass them here.search_calls_by_opportunityFind calls linked to specific CRM Opportunities by ID or name substring. Requires Gong-CRM integration (Salesforce/HubSpot) — calls without CRM linkage will not match. Provide opportunityIds OR opportunityNames (or both).search_transcriptsFree-text keyword search across call transcripts within a bounded date range. Use for ad-hoc searches like "calls mentioning competitor X". For recurring terms, prefer setting up Gong Trackers in the UI and using search_calls + get_call_summary — Trackers are server-side and dramatically cheaper. Date ranges > 30 days require additional narrowing via primaryUserIds or domains. Returns sentence-level matches with speaker attribution and timestamps.get_callGet metadata for a specific Gong call including URL, direction, scope, system, and duration. Faster than get_call_summary when you only need call metadata.get_trackersList keyword tracker definitions configured in a workspace, including every tracked phrase and which side is tracked (company/customer). Call this before using the trackers filter on search_calls so you know what names exist — workspace admins set these up and naming varies (e.g., "Competitors" vs "Competitor Mentions"). Also useful to explain tracker hits that appear in call summaries.get_userGet a specific user profile including name, email, title, phone, and settings. Use to resolve user IDs returned from call data.search_usersSearch and filter users by IDs or creation date. More flexible than list_users for resolving specific user IDs from call data.- +3 more on the listing page
Search Console MCP tools 25
get_startedStart here. Returns a complete map of this server's capabilities, active platforms, and recommended workflows. Call this once at the beginning of any session.sites_listList verified web properties across Google Search Console, Bing Webmaster Tools, or GA4.sites_manageAdd or delete a web property from Google Search Console or Bing Webmaster Tools.accounts_manageManage Google Search Console service accounts and site permissions.sitemaps_listList submitted XML sitemaps and status for a site.sitemaps_submitSubmit a new XML sitemap to Google Search Console and/or Bing Webmaster Tools.sitemaps_deleteDelete a sitemap from Google Search Console or Bing Webmaster Tools.analytics_queryUnified search performance query replacing single-dimension tools. Supports queries, pages, countries, devices, and search appearances.analytics_comparePeriod-over-period search performance comparisons, trends, and traffic drop attributions.analytics_anomaliesDetect search traffic anomalies across Google and Bing.analytics_advancedGoogle Analytics 4 (GA4) e-commerce, realtime metrics, user behavior, and conversion funnels.genai_query_insightsDetect likely generative-AI / AI-Mode / conversational fanout queries across Google and Bing. Because neither search engine exposes generative-AI citation data via its public API yet, this matches heuristic patterns (prompt verbs, follow-ups, conversational phrasing) on regular query-level performance data; it is an undercount, not an official report.- +13 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gongio MCP
{
"mcpServers": {
"gongio-mcp": {
"command": "npx",
"args": [
"-y",
"gongio-mcp"
],
"env": {
"GONG_ACCESS_KEY": "YOUR_GONG_ACCESS_KEY_HERE",
"GONG_ACCESS_KEY_SECRET": "YOUR_GONG_ACCESS_KEY_SECRET_HERE"
}
}
}
}
Search Console MCP
No confirmed install command for Search Console MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Gongio MCP is categorized under Customer Data Platforms and uses a local stdio subprocess. Search Console MCP belongs to Customer Data Platforms and uses an install path we have not confirmed yet. Pick Gongio MCP for customer data platforms work and Search Console MCP for customer data platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Search Console MCP has no confirmed install command yet — follow its own setup instructions.
Gongio MCP has no declared pricing — check the project's own site. Search Console MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gongio-mcp and saurabhsharma2u-search-console-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gongio MCP has a quality signal of 64/100 (Good) with 2 views, 0 installs and 22 GitHub stars. Search Console MCP has 65/100 (Great) with 4 views, 0 installs and 306 GitHub stars.