Skip to main content
Glama
deadrime

posthog-toolkit-mcp

by deadrime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to posthog-toolkit-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-postgres

      4l3x31s
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to inspect PostgreSQL schemas, run read-only queries and explain plans, and, when explicitly permitted, execute writes and DDL on a per-project database with layered safety controls.
      MIT

    • Read-only Analytics MCP Server

      Carlosatom8
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables analytics agents to run validated read-only SQL against a warehouse API with enforced row limits, required JSON responses, and secret-safe audit metadata.
      MIT

    • mcp-server-postgres

      ofershap
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query PostgreSQL, inspect schemas, and explain queries, designed for local and development databases with read-only safety by default.
      36 npm
      MIT

    • mcp-read-only-sql

      lukleh
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides secure read-only SQL access to PostgreSQL and ClickHouse databases with built-in safety features like read-only enforcement, timeouts, and managed result files.
      286 PyPI
      MIT

    • pg-readonly-mcp

      MadlyFriese
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only exploration of a Postgres database using natural language, with multiple safety layers to prevent any modifications.
      5
      -

    • DuckDB MCP Server

      poovenp
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables running read-only SQL queries and exploring DuckDB databases through MCP tools like listing tables, describing schemas, and fetching paginated data.
      -
    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

    A4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct area—definitions, projects, HogQL querying, replays, and generic REST access—so an agent can usually choose correctly. The only mild overlap is between posthog_query and posthog_api_get, but the HogQL vs REST distinction is clearly drawn.

    Naming Consistency3/5

    All tools share a posthog_ prefix and snake_case, but the pattern is mixed: event_definitions, projects, property_definitions, and replays are resource nouns, while posthog_query is an operation and posthog_api_get introduces a verb suffix. It is readable but not a consistent verb_noun scheme.

    Tool Count5/5

    Six tools cover the core PostHog introspection and querying use cases without padding. The generic posthog_api_get tool avoids the need for many narrowly-scoped REST endpoint tools.

    Completeness4/5

    Event/property definitions, project selection, HogQL querying, session replays, and a generic REST GET cover the main read and analysis workflows. Write/update operations are not exposed through the REST wrapper, but that appears intentionally out of scope for this query-oriented toolkit.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources