mcp-matomo and mixpanel-mcp-server
These are competitors—both provide MCP servers that integrate distinct analytics platforms (Matomo vs. Mixpanel) into Claude, allowing users to query analytics data through AI, so selection depends on which analytics backend a user already operates.
About mcp-matomo
FGRibreau/mcp-matomo
A Model Context Protocol (MCP) server that exposes your Matomo Analytics API to Claude and other MCP-compatible AI assistants.
Built in Rust with dynamic API introspection, the server automatically discovers and exposes all Matomo API methods as MCP tools at startup, or alternatively loads pre-generated OpenAPI specifications for faster initialization. It communicates via stdin/stdout transport with Claude Desktop and other MCP clients, enabling natural-language queries about analytics data like visitor counts, traffic sources, page performance, and geographic demographics without hardcoding individual API endpoints.
About mixpanel-mcp-server
moonbirdai/mixpanel-mcp-server
MCP server for Mixpanel Analytics integration with AI assistants. Enables Claude and other MCP clients to track events, pageviews, and user profiles through conversational interfaces.
Implements four prefixed tools (mixpanel_track_event, mixpanel_track_pageview, mixpanel_track_signup, mixpanel_set_user_profile) that communicate via stdio transport with Claude Desktop and any MCP-compliant client. Supports custom event properties, user profile management with Mixpanel's reserved property syntax ($name, $email), and optional referrer tracking for pageviews, with configuration via environment tokens and debug logging capabilities.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work