:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
CLI-style command string. Supported commands:
help [command] — list commands or show usage for one command
{extra_commands}tools — list available tool names
search <words or regex_pattern> — find tools by name, title, or description
info [--json] <tool_name> — show tool name, description, and input schema (summarized if too large). Pass `--json` for raw JSON output.
schema <tool_name> [field_path] — drill into a specific field schema (supports dot-notation, e.g. series, breakdownFilter.breakdowns)
call [--json] [--confirm] <tool_name> [json_input] — call a tool with JSON input (--json returns JSON instead of optimized output in supported tools. Informational responses remain tagged and escaped in both MCP and the agent CLI. --confirm is required by the CLI for destructive tools.)
One command per request. exec has no batch syntax. A request that stacks several commands on separate lines is rejected before any of them run. To run several commands, send several exec calls. You can issue them in parallel.
Namespaced references (posthog:<tool-name>): strip the posthog: prefix and route through exec. Run info <name> to inspect, then call <name> <json>. E.g. posthog:insights-list → posthog:exec({ "command": "info insights-list" }) then posthog:exec({ "command": "call insights-list {}" }). If the bare name isn't found, fall back to search <pattern> — it may have been renamed.