MCP OAuth & EMA debugger
MCP OAuth & EMA debugger: debug every flow, request by request.
An error message tells you authentication failed. The debugger shows you why, visualizing each step of the exchange between client, MCP server, and authorization server. It reads both personal OAuth and enterprise EMA flows, so a 401 points to the exact step that broke, not just a status code.
From error message to debugger
Step-by-step OAuth flow
Watch each step of the exchange between the client, MCP server, and authorization server, and see exactly where a request arrives without an access token and returns a 401.
Spec conformance checks
Guided conformance checks across the four OAuth spec versions (2025-03-26, 2025-06-18, 2025-11-25, 2026-07-28), including Dynamic Client Registration, so your server works with supported client variants.
EMA debugger
EMA (Enterprise-Managed Authorization) is the broader enterprise authorization model extending OAuth. Identity providers like Okta provision access centrally using XAA (Cross-App Access), the specific multi-app flow. The EMA debugger walks that XAA flow step by step.
Debug your auth flow locally
Launch the inspector, connect your OAuth-protected server, and watch the flow.
# Launch the inspector and step through your server's OAuth flow
npx @mcpjam/inspector@latestFrequently asked questions
It visualizes each step of the OAuth exchange between the client, MCP server, and authorization server, so instead of learning only that auth failed, you see which step failed and why, which is the information you need to fix it.
It runs guided conformance checks across the four OAuth spec versions (2025-03-26, 2025-06-18, 2025-11-25, and 2026-07-28), including Dynamic Client Registration, so a server can be verified against supported variants a client might use.
OAuth handles personal authorization. EMA (Enterprise-Managed Authorization) is the broader enterprise authorization model extending it for organizations. Identity providers like Okta grant access centrally using the specific XAA (Cross-App Access) flow, so users get connected servers on first login. The EMA debugger visualizes those XAA flows step by step.
Make your auth flow readable.
Watch every step of the OAuth exchange and find the exact point of failure. Free and open source.
Open source · no credit card · ~2 min