You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TUI / mcpdo: decode and show access-token claims #2845
Most OAuth problems with an MCP server — wrong audience, missing scope, expired token — are visible in the access token itself, but the TUI Auth tab and mcpdo show the token only as an opaque (truncated) string.
Solution you have in mind (optional)
When the access token is a JWT, decode (without verifying) and show issuer, audience, subject, scopes, issued-at and expiry, with expiry relative to now — in the TUI Auth tab and an mcpdo auth/show (or similar) command. For opaque tokens, show the expires_in / scope the token response carried.
Alternatives or workarounds you have tried
Copying the token out (TUI y) and pasting it into an external JWT decoder.
Already built it locally?
No response
Before you submit
I searched existing issues and this is not a duplicate.
This is a request for the Inspector itself, not for the MCP specification or an SDK.
Activity
cliffhall commentedon Oct 29, 2026
Triage: Priority Low (total 4)
Board: #28, Status
Incoming(awaiting maintainer review — no milestone yet).Ben-Home commentedon Oct 30, 2026
feat(tui,mcpdo): decode and show access-token claims (#2845)
fix(core): split a space-delimited string scp claim into scopes (#2845)
test: make the relative-time assertions robust to test delay (#2845)
feat(tui,mcpdo): decode and show access-token claims (#2845)
fix(core): split a space-delimited string scp claim into scopes (#2845)
test: make the relative-time assertions robust to test delay (#2845)
cliffhall commentedon Nov 5, 2026
Shipped in #2891 (merged to
v2/mainas f1e32f0).