[MCP] Linear OAuth flow fails in both CLI and Desktop App

Resolved 💬 4 comments Opened Feb 12, 2026 by fabric0de Closed Feb 12, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Codex 260210.1703, codex-cli 0.99.0

What subscription do you have?

Plus

What issue are you seeing?

I discovered a bug in the Codex Desktop App where attempting to authenticate the Linear MCP server results in no action.

In the App UI: Clicking the "Connect" or "Authenticate" button for the Linear MCP server does nothing (no browser opens, no error message).
<img width="787" height="340" alt="Image" src="https://github.com/user-attachments/assets/d73aa946-c6fc-4d00-8596-bf01748a44bd" />

In the CLI (for comparison): When I tried to reproduce this via the Codex CLI, it explicitly failed with: Error: No authorization support detected.
<img width="475" height="80" alt="Image" src="https://github.com/user-attachments/assets/15641bbd-3cf1-41d4-8325-a94cd6e3bd1e" />

What steps can reproduce the bug?

Case A: Codex CLI

Run the command to add the Linear MCP server: codex mcp add linear.
Observe the log output showing the OAuth flow starting but failing immediately with the error message.

Case B: Codex Desktop App

Navigate to the MCP settings in the Codex App.
Attempt to add or connect the Linear server via the GUI.
Click the connection button.
Result: No browser opens, and no error message is displayed in the UI.

What is the expected behavior?

For Codex CLI
When the OAuth flow starts, it should either automatically launch the default system browser or provide a clickable URI (e.g., https://linear.app...) so that the user can grant permissions. After authorization, the CLI should receive the token and confirm the connection.

For Codex App
Clicking the connection button should trigger a popup or redirect to the browser for Linear authentication. The app should then reflect the "Connected" status and list available tools (e.g., create_issue, search_issues).

Overall
The user should be able to complete the Linear integration without an "Authorization support" error, enabling the use of Linear-related tools within the Codex environment

Additional information

It appears that the OAuth callback mechanism is not properly implemented or registered within the Codex runtime for both CLI and Desktop environments. While the system detects that the server supports OAuth, it lacks the necessary "Authorization Provider" to bridge the request to a web browser.

View original on GitHub ↗

4 Comments

thehapyone · 6 months ago

Same. It fails for Atlassian as well

codex mcp add atlassian \
  --url https://mcp.atlassian.com/v1/mcp
Added global MCP server 'atlassian'.
Detected OAuth support. Starting OAuth flow…
Error: No authorization support detected

AbdallahMH · 6 months ago

I can confirm this is fixed in the alpha build.

Environment:

Codex App: 260210.1703
Stable CLI (fails): codex-cli 0.99.0
Alpha CLI (works): codex-cli 0.100.0-alpha.10

Result on stable (0.99.0):

codex mcp login linear returns:

Error: No authorization support detected

Result on alpha (0.100.0-alpha.10):

Same Linear MCP config works
OAuth URL is opened/generated correctly
Login completes successfully

Commands used:

codex --version
codex mcp add linear --url https://mcp.linear.app/mcp
codex mcp login linear

etraut-openai contributor · 6 months ago

Thanks for the bug report. This is already addressed on the main branch. Fix will be in 0.100.0.

dylancwood · 5 months ago

Incase this doesn't fix it completely: The OAuth flow for Linear's MCP server is painful in non-browser environments. It marks as "Logged out" when tokens expire, and there's no way to re-auth from a headless context.

I built Bindify to solve exactly this. You authenticate with Linear once through Bindify's web UI (or use your API Key), and it gives you a secret URL. Paste that into Codex as a remote MCP server — works in headless environments, SSH, CI, anywhere. Bindify handles Linear's token refresh server-side with atomic locking to prevent the single-use refresh token race conditions that cause invalid_grant.

Linear is also forcing all OAuth apps to refresh tokens by April 1, 2026, which is going to make this worse for any client that doesn't implement proper refresh.

Setup guide: https://bindify.dev/fix/claude-linear-auth-error -- Use promo code LINEARCODEXAUTHFIX to try it for two months free. Maybe Codex will fix their OAuth issues by then.

Disclosure: I built Bindify.