# Linear MCP Server

> Linear's official MCP server that lets any compatible AI model or agent access, create, and update Linear issues, projects, and comments via a standardized interface.

Linear's MCP server provides a standardized Model Context Protocol interface that allows any compatible AI model or agent to access your Linear workspace data in a simple and secure way. It is centrally hosted and managed by Linear, following the authenticated remote MCP spec, and supports tools for finding, creating, and updating objects like issues, projects, and comments. The server is available natively in Claude, Cursor, VS Code, Windsurf, Zed, and other clients, with the `mcp-remote` npm module available for backwards compatibility with clients that do not yet support remote MCP.

## What It Is

Linear's MCP server is a remotely hosted integration layer that bridges AI coding assistants and agent frameworks with Linear's project management platform. Rather than running locally on a user's machine, the server lives at `https://mcp.linear.app/mcp` and uses Streamable HTTP as its primary transport. Authentication is handled via OAuth 2.1 with dynamic client registration, though direct bearer token and API key authentication are also supported. The server exposes both read-write and read-only endpoints, giving teams fine-grained control over what AI agents can do.

## Supported Clients and Setup Paths

The MCP server has dedicated setup instructions for a wide range of AI clients:

- **Claude** (Team, Enterprise via claude.ai connectors; Free/Pro via Claude desktop settings)
- **Claude Code** (via `claude mcp add --transport http`)
- **Codex** (via CLI command or `~/.codex/config.toml`)
- **Cursor** (one-click install or via MCP tools directory)
- **Jules** (via Linear API key pasted into Jules MCP Settings)
- **Visual Studio Code** (via MCP: Add Server command)
- **v0 by Vercel** (via connections page)
- **Windsurf** and **Zed** (via JSON config)

For clients that do not natively support remote MCP, the open-source `mcp-remote` npm package (MIT-licensed, maintained by Cloudflare) acts as a local stdio-to-remote bridge, enabling compatibility with hundreds of additional tools.

## Enterprise Authentication and Access Control

Linear's MCP server includes enterprise-grade authentication options. Organizations using Okta can configure SAML for Linear and enable MCP enterprise-managed authentication, allowing supported external MCP clients such as Claude to authenticate users automatically using Okta-managed access policies. The server also supports multi-workspace setups by isolating OAuth sessions via separate configuration directories (e.g., using `MCP_REMOTE_CONFIG_DIR`). Read-only access can be enforced either by connecting to the `/mcp/readonly` endpoint or by requesting only the `read` OAuth scope.

## Common Use Cases and Example Workflows

The documentation provides six detailed example prompt workflows to help teams get started:

- **Roadmap planning** — Turn a planning document into a structured Linear project with issues, milestones, and relationships
- **Standup note automation** — Match standup notes to existing Linear issues and post concise update comments
- **Incoming bug investigation** — Investigate a tracked bug, identify root cause, and post findings as a comment
- **Team cycle summarization** — Summarize completed work across a cycle or timeframe for a given team
- **Timeline generation** — Build a chronological history of work around a specific topic
- **Implementation planning** — Draft and review an implementation plan, then create corresponding Linear issues and sub-issues

## Architecture and Transport

The primary transport is Streamable HTTP at `https://mcp.linear.app/mcp`. A legacy SSE endpoint at `https://mcp.linear.app/sse` remains available as a deprecated fallback for clients that do not support Streamable HTTP. The `mcp-remote` bridge package supports configurable transport strategies (`http-first`, `sse-first`, `http-only`, `sse-only`), custom headers, proxy support, tool filtering via `--ignore-tool`, and debug logging. The bridge is open source under the MIT License, originally created by Cloudflare.

## Update: Active Development and Recent Linear Changelog Activity

Linear's changelog shows active product movement as of mid-2026, including Coding Sessions on Mobile (July 30, 2026), Agent-assisted text editing (July 22, 2026), Loops for recurring agent work (July 16, 2026), and Initiative properties (June 30, 2026). The MCP server is listed as a core part of Linear's AI and agent workflow surface, alongside Linear Agent, Loops, Code Intelligence, and Triage Intelligence. The `mcp-remote` repository on GitHub was last updated July 31, 2026, with 1,535 stars and 274 forks, indicating active community adoption.

## Features
- Remote MCP server hosted at mcp.linear.app
- Streamable HTTP transport (primary)
- OAuth 2.1 with dynamic client registration
- Bearer token and API key authentication
- Read-write and read-only endpoint options
- Enterprise-managed authentication via Okta SAML
- Multi-workspace support via isolated OAuth sessions
- Tools for finding, creating, and updating issues
- Tools for creating and updating projects and comments
- Native support for Claude, Cursor, VS Code, Windsurf, Zed
- mcp-remote bridge for stdio-only clients
- Configurable transport strategies (HTTP, SSE)
- Custom header support
- Tool filtering with --ignore-tool flag
- Debug logging
- Outbound HTTP proxy support

## Integrations
Claude, Claude Code, Cursor, Visual Studio Code, Windsurf, Zed, Codex, Jules, v0 by Vercel, GitHub, GitLab, Slack, Figma, Notion, Jira, Zendesk, Intercom, Salesforce, Sentry, Discord, Zapier, Microsoft Teams, Airbyte, Google Sheets, Gong, Front

## Platforms
WINDOWS, MACOS, LINUX, ANDROID, IOS, WEB, API, VSC_EXTENSION, CLI

## Pricing
Freemium — Free tier available with paid upgrades

## Links
- Website: https://linear.app/docs/mcp
- Documentation: https://linear.app/docs/mcp
- Repository: https://github.com/geelen/mcp-remote
- EveryDev.ai: https://www.everydev.ai/tools/linear-mcp-server