pyxis-mcp
Related Servers
Alternatives to pyxis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query Google Analytics 4 data—traffic, acquisition, top pages, audiences, events, conversions, and realtime metrics—through natural language. Supports local stdio use for a single user and HTTP multi-tenant OAuth for teams.1MIT

@shieldlabs-ai/mcpofficial
AlicenseAqualityAmaintenanceEnables AI assistants to read identification verdicts, search history, summarize entities, explain risk scores, and verify webhook signatures through read-only tools over stdio or streamable HTTP.615 npmMIT- AlicenseAqualityBmaintenanceConnects AI agents to New Relic observability data through the NerdGraph GraphQL API, running locally over stdio with a standard User API key. Enables NRQL queries, entity and alert lookups, log and trace investigation, deployment correlation, and metric comparisons while staying read-only by default.14Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to query traces, sessions, exceptions, prompts, datasets, scores, and metrics for enhanced debugging and observability. Supports local stdio or HTTP deployment, selective tool loading, and read-only mode.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and developers to query traces, sessions, exceptions, prompts, datasets, annotation queues, scores, and metrics for local debugging and observability. Runs locally over stdio or HTTP with selective tool-group loading, read-only mode, and compact or file-dump output to control token usage.-
- FlicenseNot gradedqualityCmaintenanceProvides AI agents read-only analytical access to a SQLite database over stdio, with tools for listing tables, describing schemas, and running paginated SQL queries.-
TDQS
Scored across 16 tools
Most tools target clearly distinct analytics reports: acquisition, devices, engagement, requests, overview, time_of_day, and the funnel family are separable by purpose. The closest overlaps are among funnel, funnel_segments, funnel_subjects, and the property-related tools, but their descriptions make the boundaries readable. No two tools appear to do the same thing.
Names are consistently snake_case and mostly use descriptive report nouns, which is appropriate for an analytics reporting server. list_projects is the main deviation as a verb_noun discovery tool, but it is still readable and predictable within the set.
At 16 tools the server is slightly on the heavy side, but each tool maps to a meaningful analytics report rather than redundant variations. The count is reasonable for a broad web/product analytics surface, though it sits just above the ideal 3-15 range.
The surface covers discovery, settings, overview, traffic sources, engagement, devices, backend requests, event/property analysis, funnels, visits, and time-of-day reporting. Minor gaps remain around raw event querying or export-style workflows, but core analytics questions can be answered without dead ends.