Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Linear to Claude Code

Make Claude file issues and move work forward in Linear. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Linear to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Linear, you add a Linear MCP server: a small hosted service that exposes Linear's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Linear account. No API keys pasted into config files.

claude mcp add --transport http linear https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Linear once connected?

Full read-write Linear access lets Claude create issues with the right team, project, and labels, move them across workflow states, assign owners, comment on threads, and link related work. The triage and status updates that used to mean tab-switching happen where your team's work already lives, with you approving the changes.

  • Create a new issue with team, project, labels, and priority set
  • Move an issue across workflow states as work progresses
  • Assign or reassign an issue to a team member
  • Add a comment to an issue thread to capture context or decisions
  • Add an issue to a project or cycle and set its estimate
  • Search issues by query and propose batched status updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Linear access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Linear API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Linear changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Linear connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Linear connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Linear account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Linear's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Linear?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Linear account it signs in with. Revoking access is one click in Linear.

More on the Linear connector

Linear connector for claude.aiAsana + Claude CodeMonday.com + Claude CodeClickUp + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us