[hpouillot]

Problem

MCP clients cannot see or reliably filter assigned severity on Error tracking issues.

The API contract exposes severity, but the MCP response allowlist and tool guidance omit it.

PR stack

Merge in this order:

1. feat(error-tracking): expose severity in system table #83279
2. fix(error-tracking): add severity to issue query state #83107
3. fix(error-tracking): query issues by severity #86409
4. fix(error-tracking): type severity in query responses #86410
5. fix(error-tracking): expose issue severity in MCP queries #86411 - this PR

Depends on: #86410

Followed by: none

Changes

• MCP issue query results include assigned severity.
• Tool guidance documents exact, set, and unset severity filters.
• Tool guidance distinguishes date-bounded queries from all-time system-table counts.
• Generated MCP handlers and definitions update mechanically.
• No visual changes.

How did you test this code?

• Regenerated the MCP tool handlers and definitions.
• Ran the MCP tool schema tests.
• Ran the MCP tool-name validation.

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Automatic notifications

• Publish to changelog?

Docs update

Updated MCP tool guidance for severity filters and all-time counts.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Pi split the existing severity change into an MCP exposure layer under human direction.

Skills invoked: /stacking-prs, /implementing-mcp-tools, /writing-user-facing-copy, /writing-simplified-technical-english, and /writing-pr-descriptions.

[github-actions]

Hey @hpouillot! 👋

It looks like your git author email on this PR isn't your @posthog.com address (hpouillot@gmail.com). Since you're on the PostHog team, it's worth pointing your local git author email at your @posthog.com address. Why it matters:

• Consistent work identity in git history — internal tooling that attributes commits to team members keys off your @posthog.com address.
• Keeps team contributions easy to tell apart from external community ones when scanning history.

You can fix it for this repo with:

git config user.email "you@posthog.com"

Or set it globally with git config --global user.email "you@posthog.com". No need to redo this PR — just a nudge for next time. 🙂

[github-actions]

🤖 CI report

⚠️ Trunk lane — backend Python lane

This PR is assigned to the backend Python lane. It runs backend Python tests and may merge in parallel with PRs in other lanes.

ℹ️ MCP UI apps size — 33 app(s), 17661.1 KB JS

Built size of each MCP UI app (main.js + styles.css).

App	JS	CSS
debug	600.0 KB	195.2 KB
action	458.2 KB	195.2 KB
action-list	564.8 KB	195.2 KB
cohort	457.2 KB	195.2 KB
cohort-list	563.8 KB	195.2 KB
email-template	457.0 KB	195.2 KB
error-details	472.9 KB	195.2 KB
error-issue	457.9 KB	195.2 KB
error-issue-list	564.7 KB	195.2 KB
experiment	561.9 KB	195.2 KB
experiment-list	565.6 KB	195.2 KB
experiment-results	567.1 KB	195.2 KB
feature-flag	567.6 KB	195.2 KB
feature-flag-list	571.4 KB	195.2 KB
feature-flag-testing	461.4 KB	195.2 KB
inline-scan	457.7 KB	195.2 KB
insight-actors	562.6 KB	195.2 KB
invite-email-preview	456.4 KB	195.2 KB
llm-costs	559.9 KB	195.2 KB
session-recording	459.0 KB	195.2 KB
survey	458.8 KB	195.2 KB
survey-global-stats	562.7 KB	195.2 KB
survey-list	565.5 KB	195.2 KB
survey-stats	562.7 KB	195.2 KB
trace-span	457.6 KB	195.2 KB
trace-span-list	564.7 KB	195.2 KB
vision-observation-list	563.9 KB	195.2 KB
workflow	457.5 KB	195.2 KB
workflow-list	564.2 KB	195.2 KB
loops-review	461.9 KB	195.2 KB
query-results	754.8 KB	195.2 KB
render-ui	837.6 KB	195.2 KB
visual-review-snapshots	462.0 KB	195.2 KB

[trunk-io]

😎 Stack merged successfully - details.

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(error-tracking): expose issue severi..." | Re-trigger Greptile}

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-08-24 14:10 UTC	Run
prod-us	✅ Deployed	2026-08-24 16:10 UTC	Run
prod-eu	✅ Deployed	2026-08-24 23:15 UTC	Run