Issue trackersLinear

Linear MCP server and CLI with offline issues

A Linear CLI and Linear MCP server: copy your issues and projects to your computer, so your AI agent reads them offline and works with the whole Linear API.

Let your AI agent read your Linear issues, projects and comments without pasting them into the chat. The linear command-line tool copies your workspace to your computer, so the agent answers from that copy, even without the internet. When you allow it, the same tool creates and changes issues through the Linear API.

You can ask your agent which issues of a team are still in progress, what was said in the comments of ENG-12, or which issues nobody has taken. The agent finds them in the local copy and names each issue by its key. An issue you take on becomes a task in the local store, next to the tasks from your chats.

linear is both a Linear CLI for your terminal and a Linear MCP server for apps such as Claude Desktop, and for ChatGPT through a tunnel you run. You need a Linear personal API key, which you make once in Linear's settings.

On this page:

  1. What you get
  2. How it works
  3. Make a personal API key
  4. Connect and copy your workspace
  5. What it does not do yet
  6. Find a guide for your task

What you get

  • Issues without the internet. List issues by team, project, state, assignee or label, open one with its comments, and find issues, projects and comments by their words.
  • An issue becomes your task. issues assign ENG-12 adds a task for you that points at the issue, with a due date if you give one. It copies none of the issue's text, and it changes nothing in Linear.
  • Everything else Linear offers. Create an issue, change its state, add a comment, or read cycles and documents through the api group. api list names every operation.
  • You decide what the agent may change. Each profile allows, asks or refuses each kind of write. A delete or an archive needs a permission of its own, WCLINEAR_READ_ONLY=1 refuses every write, and --dry-run shows what a write would send without sending it. Over MCP nobody is there to answer, so a write set to ask goes ahead. Set permissions.api to readonly to stop that. Read more in settings.
  • Your agent connected. Install the tool's skill for a terminal agent such as Claude Code or Codex, or serve the tool over MCP to an app that connects to MCP servers.

The key stays in your system keyring, or in a private file where there is no keyring. You give it to the tool hidden or on stdin, never as an argument, so it does not end up in your shell history. Read more in security.

How it works

  • A copy on your computer. linear keeps your issues, projects and comments, with their teams, states and labels, in the local store, one file on your computer that every WireCat tool shares. Lists and search read this copy, not Linear.
  • The copy is yours. Linear shows each member a different set of teams, so the copy holds what your own key can see, and nothing of another person's private teams.
  • A sync brings in changes. The first sync copies everything. After that it reads only what changed, and once a day it notices what was deleted in Linear. Archived issues stay in the copy, marked.
  • A profile for each account. A profile is a name you choose for one Linear account, such as work. Every command that uses an account names it first: linear work issues show ENG-12.
  • The whole API as commands. Each of the 493 queries and mutations of the Linear API is a command of its own in the api group, with its own options and help. Your agent uses the same commands, at a terminal or over MCP.

Make a personal API key

In Linear, open Settings → Account → Security & access and create a personal API key. Linear lets you give the key full access or only some permissions, such as Read, and limit it to some teams. A key that can only read is enough to copy and read your workspace. To create or change issues through the tool, give it Write too. If you do not see the option, an admin of your workspace has turned off API keys for members. Linear describes the options on its API and webhooks page.

Connect and copy your workspace

  1. Install linear from npm.
  2. Sign in. work is a profile, a name you choose for one Linear account. The tool asks for the key hidden and checks it with Linear before it keeps it.
linear work session start
  1. Copy your workspace, then look at the issues that are in progress.
linear work sync
linear work issues list type:started
linear work issues show ENG-12

Run sync again later to bring in what changed.

  1. Connect your agent. A terminal agent gets the skill:
linear skill install

An app that connects to MCP servers gets the server, as described in use it.

What it does not do yet

  • WireCat's shared search does not read Linear issues yet. Find them with issues search, not together with your messages and notes.
  • It signs in only with a personal API key, not through the browser.
  • Creating and changing issues goes through the api group, one Linear operation at a time.

Find a guide for your task

TaskGuide
Install or update the toolInstall
Learn how a command is built and connect an agentUse it
Find a command or an optionCommands
Change a setting or a permissionSettings
Fix an errorWhen something goes wrong
Learn what the tool keeps and sendsSecurity
Compare it with other Linear toolsCompared with other tools