Linear MCP Server

Created By
jerhadfa year ago
A server that integrates Linear's project management system with the Model Context Protocol (MCP) to allow LLMs to interact with Linear.
Overview

What is Linear MCP Server?

Linear MCP Server is a server that integrates Linear's project management system with the Model Context Protocol (MCP), enabling large language models (LLMs) to interact with Linear's issue tracking system.

How to use Linear MCP Server?

To use the Linear MCP Server, you can install it automatically via Smithery or manually by configuring your Linear API key and server settings in Claude Desktop.

Key features of Linear MCP Server?

  • Integration with Linear's issue tracking system through MCP.
  • Tools for creating, updating, searching, and commenting on issues.
  • Flexible filtering options for issue management.

Use cases of Linear MCP Server?

  1. Automating issue creation and updates in Linear.
  2. Searching for issues based on various criteria.
  3. Managing team workloads and priorities through LLM interactions.

FAQ from Linear MCP Server?

  • Is the Linear MCP Server still maintained?

No, the Linear MCP Server is deprecated and no longer maintained. Users are advised to use the official Linear remote MCP server.

  • How do I install the Linear MCP Server?

You can install it automatically using the command npx @smithery/cli install linear-mcp-server --client claude or manually by configuring your Linear API key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jerhadf
Star
287
Language
JavaScript
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