Google Search Console vs Agent Index
A side-by-side look at the Google Search Console and Agent Index MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Search Console for search & data extraction work as a local process; choose Agent Index for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Search Console when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You want tools like
gsc_list_sites, gsc_get_site, gsc_health_check.
Choose Agent Index when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
AGENT_INDEX_DIRECTORY_URL. - You want tools like
get_network_setup, publish_index, search_index.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 49/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | AGENT_INDEX_DIRECTORY_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 20 | 10 |
| Full listing | View Google Search Console | View Agent Index |
Tools & capabilities
Google Search Console tools 20
gsc_list_sitesList all Google Search Console properties accessible with the current credentials.gsc_get_siteGet one Search Console property and its exact permission level (read-only sites.get).gsc_health_checkVerify Google Search Console read-only authentication, visible properties, configured default site, and permission levels without exposing tokens.gsc_query_search_analyticsQuery Google Search Console Search Analytics.gsc_inspect_urlInspect a URL for Google indexing status, crawl info, mobile usability, AMP, and rich results.gsc_bulk_inspect_urlsInspect multiple URLs with a conservative sequential limit and normalized URL Inspection results.gsc_list_sitemapsList sitemaps submitted for a Search Console property, including processing status and submitted/indexed counts.gsc_get_sitemapGet one submitted sitemap by full feed path, including type, fetch state, warnings/errors, and submitted/indexed content totals.gsc_get_sitemap_healthReturn an enriched read-only sitemap health summary with status totals, submitted/indexed content counts, warnings, and errors.gsc_compare_search_typesCompare performance across Search Console search types: web, image, video, news, discover, and Google News.gsc_get_data_freshnessDetect the most recent date with Search Analytics data by querying recent daily rows.gsc_monitor_indexation_freshnessRead-only monitoring snapshot for Search Analytics freshness, sitemap indexation totals, and an optional small URL Inspection sample.- +8 more on the listing page
Agent Index tools 10
get_network_setupStart here** — directory URL, configured peers, Active Nodes sections, blind-test flowpublish_indexStore a page summary and advertise agent-supplied `keywordssearch_indexDiscover peers by `keywords`, fetch records for `query`, return merged JSONquery_peer_indexQuery a known peer ID directly (bypasses DHT; uses relay hole-punch when needed)add_keywordsAdd keywords to this peer's advertised topic listremove_keywordsRemove keywords from this peer's advertised topic listset_keywordsReplace the peer's advertised keyword listfind_peers_by_keywordDHT/registry discovery only — peer IDs and multiaddrsget_peer_statusLocal peer ID, configured routing/relay, keyword and record countsget_peer_profileFetch ANP locators from another edge peer over libp2p
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.
Google Search Console
{
"mcpServers": {
"google-search-console-7": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-search-console-mcp-server"
]
}
}
}
Agent Index
{
"mcpServers": {
"agent-index": {
"command": "npx",
"args": [
"-y",
"@agent-idx/client"
],
"env": {
"AGENT_INDEX_DIRECTORY_URL": "YOUR_AGENT_INDEX_DIRECTORY_URL_HERE"
}
}
}
}
Frequently asked questions
Google Search Console is categorized under Search & Data Extraction and uses a local stdio subprocess. Agent Index belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Google Search Console for search & data extraction work and Agent Index for search & data extraction.
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.
Google Search Console has no declared pricing — check the project's own site. Agent Index has no declared pricing — check the project's own site. 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 google-search-console-7 and agent-index as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Search Console has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Agent Index has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.