mcporter OAuth auth fails with 401 before browser opens (Notion/Linear MCP)
mcporter 0.7.3 fails to complete OAuth for Notion and Linear MCP servers: after detecting OAuth, it retries the SSE endpoint and exits with
SSE error: Non-200 status code (401)before the browser ever opens. Reproduced on macOS 15.6 (Sequoia) with Node v22.22.0, both withmcporter auth notion-personalandmcporter auth linear, with or without--reset. Importing the Notion MCP from Claude Code hits the same 401, while Claude Code itself authenticates the server successfully.Originally asked on GitHub: https://github.com/openclaw/mcporter/issues/79
5 answers
Fixed upstream: a maintainer verified on current main (commit 0e50f2b, 2026-05-04) that the old 401-before-browser failure is gone. mcporter 0.7.3, where the bug was reproduced, predates the fix, so retry with a build from current main. In the verification (performed with a fake macOS
openshim so no real browser launched),mcporter auth notion --json --oauth-timeout 1500reached a Notion authorization URL and timed out as expected, andmcporter auth linear --json --oauth-timeout 1500did the same for Linear. The failure stringSSE error: Non-200 status code (401)no longer appeared, and the behavior is covered by the auth/list regression suite on main.The thread also confirmed the MCP servers were not at fault: Claude Code successfully authenticated the same Notion server. Editing the config file to add the Notion MCP did open a browser, but the flow ended in an error callback link and did not complete. One commenter reproduced the 401 with the Notion MCP imported from Claude Code, on macOS 26. If a provider still fails before producing an authorization URL on current mcporter, the maintainer asks that you open a fresh issue.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Ran
mcporter auth notion-personalaftermcporter config add notion-personal https://mcp.notion.com/mcp, plusmcporter auth linear, with and without--reset, on mcporter 0.7.3 (macOS 15.6, Node v22.22.0). The browser never opened; both failed withSSE error: Non-200 status code (401).Source: https://github.com/openclaw/mcporter/issues/79 (opens external site)
Did this work for you?What @earmer tried on GitHub (Partly worked)
Edited the config file to add the official Notion MCP and ran the flow. A browser window opened and looked authenticated, but the flow ended with an error callback link, so authorization did not complete.
Source: https://github.com/openclaw/mcporter/issues/79#issuecomment-3932102450 (opens external site)
Did this work for you?What @earmer tried on GitHub (Didn't work)
Imported the Notion MCP from Claude Code and ran auth. Same result: 401 before the browser opened. Claude Code itself could authenticate the server, ruling out a server-side bug.
Source: https://github.com/openclaw/mcporter/issues/79#issuecomment-3932102450 (opens external site)
Did this work for you?What @steipete tried on GitHub (Worked)
Maintainer verified the fix on current main (0e50f2b) using a fake macOS
openshim:mcporter auth notion --json --oauth-timeout 1500andmcporter auth linear --json --oauth-timeout 1500both reached an authorization URL and timed out as expected; the old 401 string did not appear.Source: https://github.com/openclaw/mcporter/issues/79#issuecomment-4368724182 (opens external site)
Did this work for you?
Related questions
- mcporter generate-cli fails: esbuild Could not resolve commander/mcporter
- mcporter auth linear returns 401 SSE error; workaround using mcp-remote
- How to fix mcporter Notion MCP auth error 'SSE error: Non-200 status code (401)'?
- mcporter invalid_scope: hardcoded mcp:tools OAuth scope breaks OIDC MCP servers
- mcporter auth on headless server: OAuth URL never printed, CLI just waits