Umami MCP vs MCP Search Console — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Umami MCP vs MCP Search Console
In-depth architectural comparison of the Umami MCP and MCP Search Console MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Umami MCP
Developer Tools · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
MCP Search Console
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Umami MCP if you need specialized Developer Tools tools running via a local process. Choose MCP Search Console if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Umami MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: UMAMI_URL, UMAMI_USERNAME, UMAMI_PASSWORD, UMAMI_MCP_MODE, UMAMI_MCP_ALLOW_DESTRUCTIVE, UMAMI_MCP_ENV_FILE, UMAMI_MCP_OAUTH.
Umami MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MCP Search Console belongs to Developer Tools using local stdio subprocess. Select Umami MCP when you need capabilities focused on developer tools and MCP Search Console when you require tools for developer tools.
PERMANENTLY DELETE a website and every event ever recorded for it
umami_get_tracking_snippet
Return the ready-to-paste HTML script tag that sends data to this Umami instance for a given website.
umami_get_stats
Headline totals for a website over a period: pageviews, visitors, visits, bounces and total time on site
umami_get_pageviews
Pageviews and sessions bucketed over time, for charting traffic
umami_get_metrics
Top values for one dimension, ranked by visitor count -- top pages, referrers, countries, browsers and so on
umami_get_active_visitors
Number of visitors active on the site in the last few minutes
umami_get_realtime
Live snapshot of current activity: recent events with country, URL, browser and device, plus rollups by country, URL and referrer
+16 more tools listed on main page
MCP Search Console Tools (17)
list_accounts
List all configured GSC accounts and which is the current default.
set_default_account
Set the default account used when no account is specified in other tools.
reauthenticate
Force re-authentication for an account. Clears the cached token and re-runs
the OAuth flow (or reloads service account credentials). Useful when a token
has been revoked or you need to switch Google accounts.
list_properties
List all Google Search Console properties for the specified account.
get_site_details
Get verification and permission details for a specific GSC property.
get_search_analytics
Fetch search analytics data (clicks, impressions, CTR, position).
get_performance_overview
Get a high-level performance summary: total clicks, impressions, CTR, average position.
No dimension breakdown — use get_search_analytics for that.
compare_periods
Compare search performance between two date ranges.
Returns rows for both periods side-by-side with delta calculations.