Skip to main content
Glama
josephruocco

posthog-context-mcp

by josephruocco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to posthog-context-mcp

No user-submitted related servers found.

    Related Servers

    • Beit-MCP

      Comrade-e
      F
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server that indexes documentation from URLs/files into a vector database, enabling coding agents to search and use up-to-date library and API documentation.
      -

    • docpilot-mcp

      neromtoobad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.
      4 npm
      ISC

    • api-docs-mcp

      akshaysadanand
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI coding assistants access to up-to-date API documentation via RAG by crawling documentation sites, indexing them into a vector store, and enabling semantic queries.
      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

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search for discovery, get for full-page retrieval, and how_do_i for assembled answers. Descriptions explicitly disambiguate overlapping use cases, such as directing 'how do I' questions to how_do_i instead of search.

    Naming Consistency3/5

    The first two tools follow a verb_noun pattern (search_posthog_docs, get_posthog_doc), but how_do_i breaks the convention with a question-phrase name. This is a minor inconsistency that still leaves the tools readable.

    Tool Count4/5

    With only 3 tools, the set is lean but each tool earns its place, covering discovery, full retrieval, and synthesized answers. The count is slightly on the low side but appropriate for a focused documentation context server.

    Completeness4/5

    The tool surface covers the core needs of searching, reading, and getting direct answers from PostHog docs. Minor gaps exist, such as no ability to list or browse doc categories, but the main workflows are well-supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources