Linear MCP Integration Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Linear MCP Integration Server?

The Linear MCP Integration Server provides integration capabilities through the Model Context Protocol (MCP), allowing AI models to interact with Linear for issue tracking and project management.

how to use Linear MCP Integration Server?

To use the server, set up your environment with your Linear API key, install dependencies, and start the server either in development or production mode. You can also run it using Docker for easier deployment.

key features of Linear MCP Integration Server?

  • Create, search, and manage Linear issues.
  • Retrieve current sprint issues and workflow states.
  • Flexible filtering options for searching issues and teams.
  • Comprehensive error handling and logging.

use cases of Linear MCP Integration Server?

  1. Automating issue creation in Linear from AI models.
  2. Managing project tasks and tracking progress through Linear.
  3. Integrating Linear with other tools for enhanced project management.

FAQ from Linear MCP Integration Server?

  • How do I get my Linear API key?

You can find your API key in Linear's settings under the API section.

  • Can I run this server without Docker?

Yes, you can run the server directly on your machine by following the setup instructions.

  • What programming language is this server built with?

The server is built with TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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