Staats
Server Details
Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- MrViolets/staats-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 15 tools
Most tools target clearly distinct resources or analytic questions: site CRUD, annotation handling, overviews, funnels, journeys, and diagnostic checks are separated. A few tools like get_overview, query, and what_changed could overlap when asking 'what happened', but their descriptions differentiate the intended use well.
The CRUD tools follow a clean verb_noun pattern (create_site, delete_site, list_sites, update_site_context), but analysis tools mix bare nouns (funnel, journeys), bare verbs (query), adverb-verb compounds (compare_around), and what_* question phrases (what_broke, what_changed). Naming is readable and snake_case is consistent, but the overall convention is not uniform.
15 tools is within the well-scoped range and each tool earns its place: site management, annotation tracking, traffic overview, discovery, diagnostics, and comparison all have dedicated tools. There is no obvious redundancy or padding.
The surface covers the core domain well: sites can be created, listed, deleted, and contextualized; annotations can be recorded and listed; analytics support overview, breakdown, funnel, journey, and anomaly questions. Minor gaps exist such as no update/delete for annotations and no single-site getter separate from list_sites, but agents can work around these.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
15 tool updates
- First observed
compare_around - First observed
create_site - First observed
delete_site - First observed
funnel - First observed
get_overview - First observed
get_site_context - First observed
journeys - First observed
list_annotations - First observed
list_sites - First observed
portfolio_overview - First observed
query - First observed
record_annotation - First observed
update_site_context - First observed
what_broke - First observed
what_changed
Related MCP Connectors
Cookieless web analytics your AI agent can read: traffic, spikes and what caused them, funnels.
Privacy-first product analytics. Your agent sets up tracking and answers questions about traffic.
Cookieless web analytics an agent creates and queries: goals, funnels, revenue, SQL. Open source.
Cookieless web analytics and AI Visibility: traffic, funnels, errors, and which AI bots read you.
Related MCP Servers
- AlicenseAqualityDmaintenancePrivacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.2851 npm1MIT

hootlens-mcpofficial
AlicenseNot gradedqualityBmaintenanceSession replay and click heatmaps for AI agents. Read a site’s visits as timed narratives, find repeated or dead clicks and the JavaScript errors behind them, and measure the impact of shipped changes.977 npm2MIT- AlicenseAqualityDmaintenanceFirst-party web analytics MCP server for AI agents, providing 42 tools to query traffic, events, funnels, conversions, sources, and performance data.4040 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to access website analytics, including visitor sessions, UX friction, conversion funnels, and anomaly alerts.636 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.