How to Connect Claude Code to Linear with MCP

Connecting Claude Code to Linear lets Claude find, create and update issues, projects and comments while it works on the code those issues describe. Linear hosts the server and publishes a Claude Code command on its MCP docs page.

Checked against: Linear's MCP server docs and Claude Code's MCP documentation on 28 October 2026. eSEOspace did not run these steps; menus can change, so follow the vendor's page if it differs.

Before you start

You need Claude Code installed and a Linear account in the workspace you want Claude to use.

Linear's server uses Streamable HTTP and OAuth 2.1 with dynamic client registration. That means Claude Code can register itself and send you to a browser sign-in, with no keys to create.

Decide whether Claude should write. Linear says read-write access is the default. If Claude only needs to read issues for context, use one of the read-only options below.

If you use Okta, Linear supports enterprise-managed authentication. An admin configures SAML for Linear through Okta, then turns on MCP enterprise managed authentication in Linear's settings.

Steps

Option A: Read-write with OAuth

1. In your terminal, run Linear's command:

claude mcp add --transport http linear-server https://mcp.linear.app/mcp

1. Open a Claude Code session with claude.
2. Run /mcp, select linear-server and go through the authentication flow in your browser.

Option B: Read-only endpoint

Linear documents https://mcp.linear.app/mcp/readonly, "which only ever exposes read tools." Linear doesn't print a Claude Code command for it, so this is Claude Code's generic form for a remote URL:

claude mcp add --transport http linear-readonly https://mcp.linear.app/mcp/readonly

Then sign in through /mcp as above.

Option C: API key

Linear says the server accepts an API key or OAuth token in the Authorization: Bearer <yourtoken> header. For a read-only key, create a Linear API key with only the Read permission. Built from Claude Code's documented --header form:

claude mcp add --transport http linear-server https://mcp.linear.app/mcp \
  --header "Authorization: Bearer YOUR_LINEAR_API_KEY"

Keep the key out of shared files. See Claude Code secrets management.

Check that it works

Run claude mcp list and look for ✔ Connected. Inside a session, /mcp shows Linear's tools. Linear doesn't publish a full tool list, but it says the tools cover "finding, creating, and updating objects in Linear like issues, projects, and comments."

Example prompts:

• "Using Linear, list the open issues assigned to me in the current cycle." (reads issues)
• "Summarize what my team completed in the last Linear cycle." (based on Linear's "Team cycle summarization" use case)
• "Investigate LIN-123 against this codebase, then post your findings as a comment on the issue." (based on Linear's "Incoming bug investigation" use case; this one writes a comment)

Linear's docs page has longer example prompts for roadmap planning and standup notes. Several ask the agent to show proposed changes before applying them, which is a good habit.

Permissions and safety

Linear gives three ways to keep Claude read-only:

1. Connect to https://mcp.linear.app/mcp/readonly.
2. Use the normal endpoint but request only the read OAuth scope. Linear says that token "can't reach write APIs."
3. Use a Linear API key with only the Read permission.

In Claude Code, you can also keep write tools on ask with permission rules. Rules for this server start with mcp__linear-server__.

Issue text is written by other people and can carry hidden instructions. Read prompt injection in Claude Code, approval fatigue and the MCP Security Center.

If it doesn't work

Linear's FAQ covers these:

• Internal server error on connect. Linear says to clear saved auth with rm -rf ~/.mcp-auth, then connect again. You may also need a newer Node version.
• Connection dropped or not responding. Disconnect and reconnect the server. In Claude Code, open /mcp and reconnect, or remove and re-add it. Linear says this doesn't affect your data.
• Several workspaces. Linear says reconnecting alone doesn't switch workspaces in an existing auth session, so each workspace needs its own authentication context. For clients that manage their own auth storage, Linear says to check the client's documentation. Claude Code's MCP docs don't cover this case, so use Clear authentication in /mcp and sign in to the other workspace when you switch.
• WSL on Windows. If Streamable HTTP fails in WSL, Linear documents an SSE fallback through mcp-remote.
• Old /sse URL. Use https://mcp.linear.app/mcp for new setups.

Next step

Read the Linear MCP server profile for endpoints and auth options. More setups are in the connection guides hub, including Cursor with Linear. Pair it with Claude Code and GitHub so issues and pull requests sit side by side.

Frequently asked questions