How to connect Linear to your AI assistant with MCP

TL;DR:

• Connecting Linear to your AI assistant lets you manage issues, update statuses, and triage backlogs directly from your chat interface.

• Native MCP server setups require manual configuration and ongoing token maintenance.

• Composio provides a managed MCP gateway that routes your AI assistant's requests across 1,000+ apps, with authentication, token refresh, and governed execution handled automatically.

• This guide walks you through connecting Linear to Claude, ChatGPT, and Cursor.

Every time you switch from your AI assistant to Linear to copy-paste an issue description, check a status, or update a priority, you lose the thread of whatever you were actually thinking about. For solo operators managing a busy backlog, these micro-interruptions compound quickly across a working day.

The Model Context Protocol (MCP) fixes this by letting your AI assistant read from and write to Linear directly inside the chat window. But connecting the two reliably is where most setups fall apart: API tokens require maintenance, tool calls need consistent routing to the right app and method, and execution errors surface with no clear signal.

Solving context switching with Linear MCP

How Linear MCP bridges AI and data

MCP is a way for your AI assistant to plug into other apps directly. Think of it as the nervous system between your AI's reasoning layer and the external tools it needs to act on. With it, Claude or Cursor can read your backlog, create issues with proper labels, move cards through your workflow, and assign work to teammates, all from a single prompt.

Here's what happens when you use our Linear MCP server: you send a message to Claude, Claude identifies that it needs a Linear tool call, our gateway's Tool Router directs that request to the correct Linear method, executes it using your stored and automatically refreshed credentials, and returns a structured, LLM-friendly response for Claude to act on.

The table below compares your three main options before you commit to a setup path:

Table 1: MCP setup decision matrix

How to connect Linear to Claude Cowork

Prerequisites

→ Claude Desktop with Cowork available
→ A Linear account
→ A Composio connection

1. Open Customize

→ In Claude Desktop, click Customize in the left sidebar
→ Select Connectors
→ Click the + icon at the top

2. Add the Composio MCP server

→ Click Add custom connector
→ Paste this Composio MCP server URL: https://connect.composio.dev/mcp

3. Authorize in your browser

→ Click Connect
→ You will be redirected to a browser window
→ Authorize Composio to continue

4. Connect your Linear account

→ Go back to Cowork
→ Ask the agent to connect to Linear or give it any Linear-related task
→ For example: “Create a new bug for team Mobile”
→ Or: “Add a comment to issue LIN-123”
→ Or: “List all cycles for the Design team”
→ Cowork will prompt you to authenticate and authorize access
→ Once authorization is complete, Composio’s tools are available in Cowork and your Linear account is ready to use

How to connect Linear to ChatGPT

Prerequisites

→ A ChatGPT account with access to ChatGPT Work
→ Access to the Linear workspace you want to connect
→ Composio MCP
→ Your Linear account credentials

1. Open the MCP settings

→ In ChatGPT Work, go to Settings
→ Open the Plugins section
→ Inside the Plugins page, click the MCP tab

2. Add the server

→ Click Add server
→ In the Name field, enter Composio
→ For Type, select Streamable HTTP
→ In the URL field, paste https://connect.composio.dev/mcp
→ Click Save
→ The Composio server will now appear in your MCP plugins list

3. Authenticate

→ Click Authenticate
→ Log in via Composio
→ Click Allow access to authorize ChatGPT Work to use your Composio account

4. Start using Composio

→ Composio tools are now available in ChatGPT Work
→ Ask ChatGPT Work to work with your Linear account
→ ChatGPT Work will run the Linear actions you authorize

How to connect Linear to Cursor

Prerequisites

→ Cursor
→ A Linear account
→ Composio MCP
→ Access to your Cursor mcp.json configuration

1. Install with one click

→ Click the “Install in Cursor” button
→ Composio will be added to Cursor

2. Or add manually (advanced)

If you're comfortable editing config files directly, you can add Composio to Cursor by hand instead. Skip this step if the one-click install worked.

→ Open .cursor/mcp.json in your project root
→ Or open ~/.cursor/mcp.json for a global configuration
→ Add the following configuration:

→ "servers": {
→ "composio": {
→ "type": "http",
→ "url": "https://connect.composio.dev/mcp"
→ }
→ }

3. Authorize

→ Restart Cursor
→ Open MCP Tools settings
→ Click “Connect” next to Composio
→ A browser window will open
→ Authorize Composio

4. Connect your Linear account

→ Go back to Cursor
→ Ask the agent to connect to Linear or give it any Linear-related task
→ For example: “Create a new bug for team Mobile”
→ Or: “Add a comment to issue LIN-123”
→ Or: “List all cycles for the Design team”
→ Cursor will prompt you to authenticate and authorize access to Linear
→ Once authorization is complete, Composio tools are available in Cursor
→ Your Linear account is ready to use

Automate your Linear tasks with AI

Once Linear is connected, these three prompt templates automate the most common project management tasks. Copy them and modify for your workflow.

Automate issue creation via Linear MCP

Create a Linear issue with:
- Title: "Fix null pointer exception in payment processor"
- Description: "Service crashes when payment_method is null during checkout.
  Reproducible on orders over $500."
- Label: "Bug"
- Priority: "Urgent"
- Team: Engineering

Claude will call our Linear toolkit, format the request as structured JSON, and return the new issue identifier with a confirmation.

Update issue status and priority

Move issue ENG-104 to "In Progress" and set priority to "High."
Assign it to the user with email dev@yourteam.com.

Claude identifies the relevant Linear methods for the status update and the assignment separately, then executes them in sequence as a single response.

Triage and organize your backlog

Show me all unassigned Linear issues in the Engineering team.
Group them by estimated effort if that label exists,
and suggest a priority order based on the descriptions.

Claude returns a structured analysis you can review, then follow up with additional prompts to apply the suggested priorities, or ask Claude to apply them directly.

Resolving common Linear MCP connection errors

If your connection breaks or tool calls fail, work through these four fixes in order: expired or invalid tokens, incorrect access levels, missing connections, and execution failures. Most issues resolve after a reconnect or client restart.

Fixing expired or invalid tokens

If you see an authentication error, the initial connection likely used a Linear API key that has since been revoked. To fix it: go to your Composio dashboard, find the Linear connection under connected apps, disconnect it, and re-authorize using your current API key from Linear > Settings > Account > Security & Access.

Managing Linear MCP access levels

Your Linear API key determines what the AI assistant can access. A read-only key works for backlog queries but prevents issue creation and status updates. A read-write key is needed for the automation prompts in this guide.

To adjust scopes, generate a new key in Linear's API settings with the permissions you want, then update the connection in your Composio dashboard.

Fixing missing Linear MCP connections

If your AI assistant can't find the Linear connection:

1. Re-authenticate via the Composio dashboard by disconnecting and reconnecting the Linear app.

2. Restart Claude Desktop or Cursor completely (quit the application, not just close the window).

3. Verify the API key hasn't been revoked in Linear's settings under Security & Access.

Fixing Linear MCP execution failures

Table 2: Common Linear MCP error codes and quick fixes

Quick fixes for common workflow issues

This covers the most common workflow question from solo operators setting up Linear MCP for the first time.

How to refresh your Linear MCP token

Our auth layer handles token refresh automatically, including OAuth token rotation, per the Linear toolkit documentation. If you need to manually reset the connection after intentionally rotating your Linear API key, go to your Composio dashboard, navigate to connected apps, find Linear, and select Reconnect. This re-runs the one-click authorization flow and stores the updated credentials.

Security implications

When you connect Linear to an AI assistant, you're giving that assistant access to your project data, team workflows, and potentially sensitive business information. The security boundaries are worth knowing.

What gets exposed: The AI assistant can read all issues, comments, and project details accessible to the Linear API key you provide. If you use a personal API key with full workspace access, the assistant inherits those permissions. A compromised key or misconfigured assistant prompt could expose confidential project information.

How Composio reduces risk: Our managed gateway handles credential storage using SOC 2 and ISO 27001 certified infrastructure, with all data encrypted at rest and in transit. Your Linear API key is never exposed in local config files where it could be accidentally committed to a repository or accessed by unauthorized users. Zero data retention is available as a Pro-and-above add-on; without it, standard retention policies apply. All data is encrypted at rest and in transit regardless of plan.

What you control: Generate read-only Linear API keys when you only need backlog queries and status checks. Reserve read-write keys for workflows that create or update issues. Rotate keys quarterly or after team member departures. Review Linear's API access logs regularly to monitor which requests your assistant is making.

Risk of self-hosted alternatives: Running a native MCP server stores your Linear credentials in local configuration files. If your development machine is compromised or your repository is accidentally made public, those credentials are exposed. Managed gateways centralize credential storage and rotation, reducing the attack surface for most teams.

Create your free Composio account, no credit card required. The free tier covers 100,000 tool calls per month and offers unlimited connections.

FAQs

Does Composio store my Linear data?

It depends on your plan. Zero data retention is available as a Pro-and-above add-on; on the free tier, standard retention policies apply. Regardless of plan, all data is encrypted in transit and at rest, and we are SOC 2 and ISO 27001 certified.

What should I do if Claude Desktop throws an "MCP connection lost" error?

This happens when Claude needs a restart to load new MCP configurations. Save your work, fully quit Claude Desktop including from the system tray, and reopen it to re-establish the connection.

Key terms glossary

Model Context Protocol (MCP): A universal connector that lets AI assistants read from and write to your apps without custom integration code.

Managed auth layer: The execution infrastructure we provide that routes tool calls to the right app and method, handles OAuth flows, API keys, and token refreshes automatically, and returns structured responses your AI assistant can act on, so your connections stay live and your agent logic stays simple.

Tool Router: A Composio feature that automatically directs your AI assistant's natural language requests to the correct connected application and API method without requiring custom conditional logic in your configuration.

Zero data retention: A setup where tool call data passes through our gateway to execute a request but isn't stored on our servers afterward.

Personal API key: A credential generated inside Linear at Settings > Account > Security & Access that grants an application access to your Linear workspace at the scope you define.