Repository navigation
posthog-v7.86.0
Immutable
release. Only release title and notes can be modified.
Minor changes
-
0aa5df1 MCP analytics now matches the cross-SDK MCP spec ahead of 1.0:
instrument()sends$mcp_unknown_toolinstead of a failed$mcp_tool_calland$exceptionwhen atools/callnames a tool your server never registered. Insights that count failed tool calls stop counting these. A call naming no tool sends nothing. A raw low-level server has no registry the SDK can read, so a failed call there stays a failed tool call.- FastMCP's stock logging, timing, error-handling, and similar middleware no longer turns off
llm_modelinjection on standalonefastmcp.FastMCP. - Manual capture without a
session_idnow sends a freshses_session id and uses it as thedistinct_id, instead of no$session_idand ananonymousperson. - Truncated string properties now fit their limit with the
...marker included, so$mcp_tool_nameand other names stop at 256 characters instead of 259. — Thanks @lucasheriques!
-
5f2ee56
posthog.mcpis now stable. From this release, a minor or patch release ofposthogno longer makes breaking changes to theposthog.mcpAPI, renames or removes a$mcp_*event or property, changes its type, or changes which requests send an event, so your saved insights keep working across upgrades. New events and properties can still arrive in minor releases. Upgrading needs no code change. — Thanks @lucasheriques!
Patch changes
- d8a7ff0 On FastMCP 2.x servers with middleware,
posthog.mcpno longer tries to read the advertised tool schema on each call. FastMCP 2.x can only list tools through request middleware, which can spend rate limits, so the lookup failed and logged an error on every call. Argument names there stay redacted in$mcp_input_keys, as before. — Thanks @lucasheriques!