Skip to main content
Glama
devhuang0714

umeng-openapi-mcp-server

by devhuang0714
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to umeng-openapi-mcp-server

No user-submitted related servers found.

    Related Servers

    • aptabase-mcp

      billylo1
      A
      license
      A
      quality
      F
      maintenance
      Unofficial MCP server that lets AI agents query Aptabase analytics using cookie-authenticated dashboard endpoints, providing tools for metrics, events, and sessions.
      17
      1
      MIT

    • umami-mcp-server

      frontedu
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Umami Analytics that provides read-only tools to query website stats, events, sessions, reports, and more, enabling natural language analytics queries.
      16 npm
      3
      MIT

    • analyga

      jyswee
      A
      license
      Not graded
      quality
      C
      maintenance
      Agent-first analytics MCP server for querying stats, funnels, and web/agent traffic, with server-side event ingestion and self-serve signup.
      78 npm
      -

    • Mixpanel MCP Server

      T-Campbell18
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides access to the Mixpanel REST API, enabling AI agents to query events, funnels, retention data, and user profiles. It allows users to perform complex analytics tasks and export raw event data through natural language prompts.
      16
      6 npm
      MIT

    • @byterover/umami-mcp

      campfirein
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for Umami analytics, enabling natural language queries of website stats, traffic trends, events, sessions, and analytics reports.
      13
      10 npm
      1
      Elastic 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 40 tools

    Disambiguation2/5

    Many tools have overlapping purposes, e.g., multiple tools for active users (umeng_get_active_users, umeng_uapp_get_active_users, umeng_uapp_get_active_accounts) and daily data (umeng_get_daily_data, umeng_uapp_get_daily_data, umeng_uapp_get_today_data). This makes it difficult for an agent to distinguish which tool to use.

    Naming Consistency3/5

    Naming follows two patterns: 'umeng_get_*' and 'umeng_uapp_*', with variations like 'find' vs 'get'. While each pattern is internally consistent, the mix creates inconsistency. The snake_case convention is consistent overall.

    Tool Count3/5

    40 tools is high but justifiable for a comprehensive analytics platform. However, many tools are redundant (e.g., multiple wrappers for similar data), suggesting the set could be streamlined.

    Completeness4/5

    The tool set covers a wide range of analytics endpoints: app management, events, channels, versions, retention, and various time-based statistics. Gaps are minor (e.g., lack of update/delete for events).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources