posthog-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_posthog_docsA | Search PostHog's JS/Web SDK docs and return ranked snippets. Pure retrieval with no assembly — use this to discover what documentation exists. For 'how do I X' questions, use |
| get_posthog_docA | Fetch a full PostHog doc by path or slug, e.g. 'libraries/js/usage', '/docs/product-analytics/identify', or a full posthog.com URL. Returns the complete markdown — this can be large, so prefer |
| how_do_iA | Answer a 'how do I X with PostHog?' task with an assembled context block: the minimal set of deduplicated, ordered, cited passages that answer it, within a token budget. Prefer this over search for any implementation question — it returns roughly a quarter the tokens of a raw top-k dump with materially higher precision. Pass the task in natural language, and mention the framework if you know it ('in React') so the right variant is selected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.