MCP serverValidated

Linear MCP — plan against the real backlog

Linear's official server: read, create, and update issues from the session — so 'what should this task actually cover' is answered from the tracker, and finished work updates its own ticket.

io.linear/mcpOfficial docs →

A vetted listing, not an install — add the config to your MCP client yourself. CoSquared never writes MCP config.

Why this one

Task framing improves when the agent can read the actual acceptance criteria instead of a paraphrase — first-party and OAuth-scoped.

How to use it

  1. 1Frame tasks by pulling the real issue, not a from-memory summary
  2. 2Let the session close its own ticket when the work lands

Client config

Placeholders only — bring your own values

{
  "mcpServers": {
    "linear": {
      "url": "https://mcp.linear.app/sse"
    }
  }
}

Security notes

OAuth grants read/write over the issues your account can see — in most workspaces that is every team's backlog, including confidential projects. Issue contents flow into model context; connect a workspace you are comfortable exposing to the session.