Linear MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Linear MCP Server?

Linear MCP Server is an implementation of the Linear Model Context Protocol (MCP) that provides an interface for accessing Linear resources, enabling developers to interact with Linear's issue tracking and project management features.

how to use Linear MCP Server?

To use the Linear MCP Server, clone the repository, install dependencies, create a startup script with your Linear API key, configure it in Cursor, and start the server.

key features of Linear MCP Server?

  • Create new Linear issues with specified parameters.
  • Search for Linear issues using various filters.
  • Read Linear resources using URIs.
  • Implements rate limiting and detailed error handling.

use cases of Linear MCP Server?

  1. Automating issue creation in Linear for project management.
  2. Integrating Linear issue tracking into custom applications.
  3. Searching and retrieving issue data programmatically.

FAQ from Linear MCP Server?

  • What is required to run the Linear MCP Server?

You need to have Node.js installed and a valid Linear API key.

  • Can I use this server for multiple projects?

Yes! You can configure it to work with different Linear projects by changing the API key and settings.

  • Is there a limit on the number of requests?

Yes, the server implements a rate limit of 1000 requests per hour.

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