{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-google-search-console","slug":"google-search-console","name":"Google Search Console","type":"mcp","url":"https://github.com/ahonn/mcp-server-gsc","page_url":"https://unfragile.ai/google-search-console","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-google-search-console__cap_0","uri":"capability://data.processing.analysis.search.analytics.data.retrieval.with.25x.api.limit.expansion","name":"search analytics data retrieval with 25x api limit expansion","description":"Retrieves search performance data from Google Search Console with pagination logic that aggregates up to 25,000 rows per query, compared to the standard Google API limit of 1,000 rows. Implements a service layer abstraction (SearchConsoleService) that wraps the Google Search Console API and handles multi-page result aggregation transparently, allowing AI assistants to analyze complete datasets without manual pagination or row-limit workarounds.","intents":["I need to analyze all search queries driving traffic to my site, not just the top 1,000","I want to export complete search performance data for a date range without hitting API limits","I need to identify long-tail query opportunities across my entire search footprint"],"best_for":["SEO professionals managing large websites with 10,000+ monthly search queries","AI agents automating SEO analysis and reporting workflows","Data analysts building custom dashboards from Search Console data"],"limitations":["Pagination aggregation adds latency proportional to dataset size; 25,000-row retrieval may take 10-30 seconds depending on network conditions","Google Search Console API rate limits still apply per service account; high-frequency queries may be throttled","Data is read-only; no capability to modify search appearance or indexing settings through this tool"],"requires":["Node.js 18.0.0 or higher","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console read access (via GOOGLE_APPLICATION_CREDENTIALS environment variable)","Valid site property registered in Google Search Console"],"input_types":["site URL (string, e.g., 'https://example.com')","date range (startDate, endDate as ISO 8601 strings)","optional filters (query patterns, URL patterns, device type, country)"],"output_types":["JSON array of search analytics records with fields: query, page, clicks, impressions, ctr, position"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_1","uri":"capability://data.processing.analysis.regex.based.query.and.url.filtering.for.search.analytics","name":"regex-based query and url filtering for search analytics","description":"Applies regex pattern matching to filter search queries and URLs in analytics results, extending beyond Google Search Console's built-in basic operators. The SearchConsoleService layer intercepts raw API responses and applies client-side regex filtering before returning results, enabling complex pattern-based queries like 'all URLs matching /blog/[0-9]{4}/' or 'queries containing (buy|purchase|price)' without requiring manual post-processing.","intents":["I want to find all search queries matching a specific pattern (e.g., all 'how to' questions)","I need to analyze performance for URLs matching a regex pattern (e.g., all blog posts from 2024)","I want to exclude certain query patterns from my analysis (e.g., branded queries)"],"best_for":["SEO analysts performing advanced query segmentation and pattern-based analysis","Content strategists identifying content gaps by query pattern","AI agents building intelligent SEO recommendations based on regex-matched query clusters"],"limitations":["Regex filtering is applied client-side after API retrieval, so complex patterns on large datasets (10,000+ rows) may add 500ms-2s processing overhead","Regex syntax must be valid JavaScript RegExp; invalid patterns will cause tool execution to fail","No support for lookahead/lookbehind assertions in some regex contexts due to JavaScript engine limitations"],"requires":["Node.js 18.0.0 or higher","Valid JavaScript regex syntax for filter patterns","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console read access"],"input_types":["regex pattern string (e.g., '/blog/.*', '(buy|purchase|price)')","filter type ('query' or 'url')","site URL and date range (same as base analytics retrieval)"],"output_types":["JSON array of filtered search analytics records matching the regex pattern"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_2","uri":"capability://planning.reasoning.automated.seo.opportunity.detection.via.quick.wins.analysis","name":"automated seo opportunity detection via quick wins analysis","description":"Analyzes search analytics data to automatically identify SEO quick-win opportunities based on configurable thresholds for position, click-through rate (CTR), and impression count. The SearchConsoleService implements a Quick Wins detection algorithm that scores queries/URLs by their optimization potential (e.g., queries ranking 6-10 with high impressions but low CTR are high-priority targets for title/meta optimization), returning ranked recommendations without requiring manual threshold configuration.","intents":["I want to identify which queries I should optimize first to maximize traffic gains","I need to find pages ranking 6-10 that could move to top 3 with minor optimizations","I want to prioritize content improvements based on impression volume and current CTR"],"best_for":["SEO practitioners seeking data-driven optimization priorities","AI agents generating automated SEO recommendations and action plans","Content teams allocating limited optimization resources to highest-impact opportunities"],"limitations":["Quick Wins detection uses heuristic thresholds (position 6-10, CTR below median, impressions above threshold) that may not align with all site types or industries","Algorithm does not account for keyword difficulty, search intent, or competitive landscape; recommendations are based solely on current performance metrics","Requires sufficient historical data (minimum 7-30 days of impressions) to generate meaningful recommendations; new sites may have limited opportunities"],"requires":["Node.js 18.0.0 or higher","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console read access","Minimum 7 days of search data in Google Search Console for the target site"],"input_types":["site URL (string)","date range (startDate, endDate)","optional custom thresholds (positionMin, positionMax, ctrThreshold, impressionThreshold)"],"output_types":["JSON array of opportunity objects with fields: query, currentPosition, currentCTR, impressions, opportunityScore, recommendedAction"],"categories":["planning-reasoning","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_3","uri":"capability://automation.workflow.sitemap.submission.and.management.via.mcp.tools","name":"sitemap submission and management via mcp tools","description":"Manages XML sitemap operations for registered Google Search Console properties, including submission of new sitemaps and retrieval of existing sitemap status. Implements three dedicated MCP tools that wrap Google Search Console's sitemap API endpoints, allowing AI assistants to submit sitemaps, list all submitted sitemaps, and retrieve detailed status information (indexed URLs, errors, warnings) for each sitemap without manual console navigation.","intents":["I want to submit a new sitemap to Google Search Console programmatically","I need to check the indexing status of my sitemaps and identify any errors","I want to list all sitemaps currently submitted for my site and their health status"],"best_for":["DevOps engineers automating sitemap submission in CI/CD pipelines","AI agents managing site indexing workflows and monitoring sitemap health","SEO automation platforms integrating Google Search Console management"],"limitations":["Sitemap submission is asynchronous; Google may take 24-48 hours to fully process and index a newly submitted sitemap","No capability to delete or remove sitemaps through this tool; removal must be done via Google Search Console UI","Sitemap status reflects Google's last crawl; real-time indexing status is not available immediately after submission"],"requires":["Node.js 18.0.0 or higher","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console write access (for submission) or read access (for status retrieval)","Valid site property registered in Google Search Console","Sitemap URL must be publicly accessible and valid XML format (for submission)"],"input_types":["site URL (string)","sitemap URL (string, for submission)","optional: sitemap index URL (for listing operations)"],"output_types":["JSON object with sitemap status including: sitemapUrl, type (sitemap or sitemapIndex), lastSubmitted, lastDownloaded, indexedUrls, errors, warnings"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_4","uri":"capability://search.retrieval.url.inspection.and.indexing.status.verification","name":"url inspection and indexing status verification","description":"Inspects individual URLs to retrieve their current indexing status in Google Search Console, including whether the URL is indexed, any indexing errors, mobile usability issues, and rich result eligibility. Wraps Google's URL Inspection API through an MCP tool that accepts a URL and site property, returning detailed indexing metadata that helps diagnose why specific pages may not be indexed or appearing in search results.","intents":["I want to check if a specific URL is indexed by Google and why it might not be","I need to verify that a newly published page has been indexed","I want to diagnose mobile usability or rich result issues for a specific URL"],"best_for":["SEO specialists troubleshooting indexing issues for specific URLs","Content teams verifying new page indexation after publication","AI agents diagnosing and reporting on site indexing health"],"limitations":["URL Inspection API has rate limits (typically 600 requests per minute per property); high-volume inspection workflows may be throttled","Inspection results reflect Google's last crawl; real-time indexing status may lag 24-48 hours behind actual indexation","No capability to request immediate re-crawl or re-indexation through this tool; must use Google Search Console UI or Fetch as Google API"],"requires":["Node.js 18.0.0 or higher","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console read access","Valid site property registered in Google Search Console","URL must belong to the specified site property"],"input_types":["site URL (string, e.g., 'https://example.com')","inspection URL (string, full URL to inspect)"],"output_types":["JSON object with fields: indexStatus (indexed/not indexed), lastCrawlTime, mobileUsabilityIssues, richResultIssues, coverageStatus, crawlIssues"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_5","uri":"capability://search.retrieval.site.property.listing.and.metadata.retrieval","name":"site property listing and metadata retrieval","description":"Retrieves a list of all Google Search Console properties (sites) accessible to the authenticated service account, including site URLs, property types (domain or URL prefix), and verification status. Implements an MCP tool that calls Google's Search Console API to enumerate all properties, enabling AI assistants to discover available sites and select the appropriate property for subsequent operations without requiring manual property URL input.","intents":["I want to see all Google Search Console properties I have access to","I need to programmatically discover which sites are registered in my Search Console account","I want to verify that a specific site property is accessible before running analytics queries"],"best_for":["AI agents managing multiple properties and needing to discover available sites","Multi-site SEO platforms automating property enumeration","Developers building Search Console integrations that need dynamic property discovery"],"limitations":["Returns only properties accessible to the authenticated service account; properties owned by other accounts are not visible","Does not include detailed site metrics or performance data; only metadata (URL, type, verification status)","Property list may be large for accounts managing 100+ properties; no pagination or filtering options"],"requires":["Node.js 18.0.0 or higher","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console read access","At least one property registered in Google Search Console"],"input_types":["none (uses authenticated service account credentials)"],"output_types":["JSON array of site property objects with fields: siteUrl, propertyType (domain or urlPrefix), verificationStatus"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_6","uri":"capability://safety.moderation.schema.first.request.validation.with.zod.runtime.schemas","name":"schema-first request validation with zod runtime schemas","description":"Validates all incoming MCP tool requests against Zod schemas before execution, ensuring type safety and preventing malformed requests from reaching Google APIs. The system defines schemas for each tool's input parameters (SearchAnalytics, SitemapSubmission, UrlInspection, etc.) in src/schemas.ts, with Zod providing runtime validation that generates JSON schemas for MCP protocol compliance and catches invalid inputs with detailed error messages.","intents":["I want to ensure that tool requests are validated before hitting the Google API","I need clear error messages when I provide invalid parameters to a tool","I want to generate JSON schemas for MCP protocol compliance automatically"],"best_for":["MCP server developers building robust API integrations","AI assistant builders needing strict input validation before external API calls","Teams requiring type-safe tool definitions with automatic schema generation"],"limitations":["Zod validation adds ~5-10ms overhead per request; high-frequency requests may accumulate latency","Schema definitions must be manually maintained in sync with tool implementations; schema drift can cause validation failures","Complex nested schemas may generate verbose JSON schema output that increases MCP protocol message size"],"requires":["Node.js 18.0.0 or higher","Zod library (included in package.json dependencies)","TypeScript 4.7+ for type inference from Zod schemas"],"input_types":["JSON request payloads matching MCP tool call format"],"output_types":["validated request object (if valid) or validation error with detailed field-level error messages"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_7","uri":"capability://tool.use.integration.stdio.based.mcp.protocol.communication.with.language.agnostic.integration","name":"stdio-based mcp protocol communication with language-agnostic integration","description":"Implements the Model Context Protocol (MCP) server using stdio-based communication, allowing any client (Claude Desktop, custom agents, other LLMs) to interact with the server through standard input/output streams. The MCP server in src/index.ts handles protocol-level request/response marshaling, tool registration, and stdio setup, enabling sandboxed execution and language-agnostic client integration without requiring HTTP servers or network configuration.","intents":["I want to integrate Google Search Console with Claude Desktop or other MCP clients","I need to run the Search Console server in a sandboxed environment without exposing network ports","I want to build custom AI agents that can access Search Console data through MCP"],"best_for":["Claude Desktop users adding Search Console integration via MCP","AI agent builders implementing MCP servers for Google API access","DevOps engineers deploying MCP servers in containerized or sandboxed environments"],"limitations":["Stdio-based communication is synchronous; concurrent requests from multiple clients are serialized and processed sequentially","No built-in authentication or authorization at the MCP protocol level; security relies entirely on service account credentials and environment variable protection","Debugging stdio-based communication requires log redirection or external monitoring tools; standard debugging workflows may be limited"],"requires":["Node.js 18.0.0 or higher","MCP client implementation (e.g., Claude Desktop, custom agent)","Service account credentials in GOOGLE_APPLICATION_CREDENTIALS environment variable","MCP protocol version 1.0+ support in client"],"input_types":["MCP protocol JSON-RPC 2.0 requests via stdin"],"output_types":["MCP protocol JSON-RPC 2.0 responses via stdout"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-search-console__cap_8","uri":"capability://safety.moderation.service.account.authentication.with.google.cloud.credentials","name":"service account authentication with google cloud credentials","description":"Authenticates to Google Search Console using service account credentials loaded from the GOOGLE_APPLICATION_CREDENTIALS environment variable, following Google Cloud best practices. The SearchConsoleService layer initializes the Google API client with the service account key, enabling secure, non-interactive authentication without requiring user OAuth flows or API key management.","intents":["I want to authenticate to Google Search Console programmatically without user interaction","I need to run automated Search Console queries in CI/CD pipelines or scheduled jobs","I want to follow Google Cloud security best practices for API authentication"],"best_for":["DevOps engineers automating Search Console access in CI/CD pipelines","AI agents requiring non-interactive authentication to Google APIs","Teams managing multiple Search Console properties with service account access"],"limitations":["Service account credentials must be stored securely; exposure of the JSON key file compromises all Search Console properties accessible to that account","Service account permissions are limited to properties explicitly shared with the service account email; cannot access properties owned by other accounts","Credential rotation requires manual key management; no built-in credential refresh or rotation logic"],"requires":["Google Cloud Project with Search Console API enabled","Service account created in Google Cloud Console with Search Console API access","Service account JSON key file downloaded and stored securely","GOOGLE_APPLICATION_CREDENTIALS environment variable pointing to the JSON key file","Service account email added as a user with appropriate permissions in Google Search Console properties"],"input_types":["GOOGLE_APPLICATION_CREDENTIALS environment variable (path to service account JSON key)"],"output_types":["authenticated Google API client instance (internal; no direct output)"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["Node.js 18.0.0 or higher","Google Cloud Project with Search Console API enabled","Service account credentials with Search Console read access (via GOOGLE_APPLICATION_CREDENTIALS environment variable)","Valid site property registered in Google Search Console","Valid JavaScript regex syntax for filter patterns","Service account credentials with Search Console read access","Minimum 7 days of search data in Google Search Console for the target site","Service account credentials with Search Console write access (for submission) or read access (for status retrieval)","Sitemap URL must be publicly accessible and valid XML format (for submission)","URL must belong to the specified site property"],"failure_modes":["Pagination aggregation adds latency proportional to dataset size; 25,000-row retrieval may take 10-30 seconds depending on network conditions","Google Search Console API rate limits still apply per service account; high-frequency queries may be throttled","Data is read-only; no capability to modify search appearance or indexing settings through this tool","Regex filtering is applied client-side after API retrieval, so complex patterns on large datasets (10,000+ rows) may add 500ms-2s processing overhead","Regex syntax must be valid JavaScript RegExp; invalid patterns will cause tool execution to fail","No support for lookahead/lookbehind assertions in some regex contexts due to JavaScript engine limitations","Quick Wins detection uses heuristic thresholds (position 6-10, CTR below median, impressions above threshold) that may not align with all site types or industries","Algorithm does not account for keyword difficulty, search intent, or competitive landscape; recommendations are based solely on current performance metrics","Requires sufficient historical data (minimum 7-30 days of impressions) to generate meaningful recommendations; new sites may have limited opportunities","Sitemap submission is asynchronous; Google may take 24-48 hours to fully process and index a newly submitted sitemap","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.28,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.041Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=google-search-console","compare_url":"https://unfragile.ai/compare?artifact=google-search-console"}},"signature":"F6yi468qtERfWAGnM9xUd9z0/PH0xbLD9WMGWL2B9unT5W0fDSX8T0NF0yH8RuioDuaKW5wS3l+co5+i3+boDA==","signedAt":"2026-06-22T15:00:17.097Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/google-search-console","artifact":"https://unfragile.ai/google-search-console","verify":"https://unfragile.ai/api/v1/verify?slug=google-search-console","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}