Skip to main content
Glama
johnnikolo

posthog-mcp

by johnnikolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to posthog-mcp

No user-submitted related servers found.

    Related Servers

    • PostHog MCP

      stuartbrameld
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with PostHog's product analytics platform through natural language, allowing users to manage feature flags, view errors, and access other platform features.
      25 npm
      1
      MIT

    • posthog-mcp-server

      friendlygeorge
      A
      license
      A
      quality
      F
      maintenance
      Connects AI assistants to PostHog to query events, persons, insights, dashboards, feature flags, cohorts, and experiments through the Model Context Protocol.
      13
      35 npm
      MIT

    • posthog-mcp

      israpasos
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with PostHog analytics platform, allowing users to list projects, create annotations, and search insights through natural language in Claude Desktop.
      5
      MIT

    • Metricairn

      rnepal2
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to query self-hosted product analytics, investigate changes with evidence and coverage checks, and use optional management tools for saved reports, goals, and keys.
      20
      1
      MIT

    • Product Pulse MCP Server

      alexalghisi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to explore a project's captured events and properties, then run trend, funnel and retention analyses and create or list saved insights. Tools are model-oriented, returning trimmed, budgeted results and actionable errors, with the project resolved from the API key or bearer token rather than passed as an argument.
      MIT
    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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct PostHog resource: feature flags, insights, persons, events, and trends. There is no overlap in functionality, making it clear which tool to use for each task.

    Naming Consistency3/5

    The naming pattern is inconsistent: three tools use 'get_', one uses 'list_', and one uses 'query_'. Furthermore, 'get_insights' suggests a single insight but actually retrieves by ID, while 'get_feature_flags' returns a list. This could cause confusion.

    Tool Count4/5

    With five tools, the server covers essential read operations for a PostHog integration. The count is reasonable but slightly on the low side for a comprehensive analytics platform; it could include a few more tools.

    Completeness2/5

    The tool surface is entirely read-only, missing create, update, and delete operations for all resources. There are no tools for managing cohorts, experiments, or dashboards, leaving significant gaps for typical PostHog workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources