MCP Linear

Created By
tacticlauncha year ago
MCP server that enables AI assistants to interact with Linear project management system through natural language, allowing users to retrieve, create, and update issues, projects, and teams.
Overview

what is MCP Linear?

MCP Linear is a server implementation that integrates Linear's project management system with the Model Context Protocol (MCP), enabling AI assistants to interact seamlessly with Linear.

how to use MCP Linear?

To use MCP Linear, you need to obtain a Linear API token and install the package via Smithery or manually. After installation, run the server with your API token to start interacting with Linear.

key features of MCP Linear?

  • Retrieve issues, projects, teams, and other data from Linear
  • Create and update issues
  • Change issue status
  • Assign issues to team members
  • Add comments
  • Create projects and teams

use cases of MCP Linear?

  1. Automating project management tasks with AI assistants.
  2. Streamlining issue tracking and updates in Linear.
  3. Enhancing team collaboration through AI-driven insights.

FAQ from MCP Linear?

  • How do I get my Linear API token?

You can obtain your Linear API token from the settings in your Linear account under 'Security & access'.

  • Is MCP Linear compatible with all AI assistants?

MCP Linear is designed to work with Cursor and Claude, among others.

  • What programming language is MCP Linear built with?

MCP Linear is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tacticlaunch
Star
81
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago