Linear

Created By
dvcrna year ago
Overview

what is Linear?

Linear is an MCP server designed for interacting with Linear's API, providing tools for managing issues, projects, and teams through Cline.

how to use Linear?

To use Linear, you need to set up the server by obtaining a Linear API token and configuring the Cline MCP settings file with the necessary server configuration.

key features of Linear?

  • Create, update, and delete issues with full field support.
  • Manage projects and associate issues with them.
  • Handle team information and states.
  • Support for bulk operations on issues.
  • Secure authentication with Personal Access Tokens.

use cases of Linear?

  1. Managing software development tasks and issues.
  2. Organizing projects and tracking progress.
  3. Collaborating with teams on project milestones.

FAQ from Linear?

  • How do I get my Linear API token?

You can obtain your token from Linear's settings under API > OAuth application.

  • Can I manage multiple Linear workspaces?

Yes! You can connect to multiple workspaces by adding the Linear MCP server multiple times with different TOOL_PREFIX values.

  • Is there support for bulk operations?

Yes, Linear supports bulk issue creation and deletion.

Server Config

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": [
        "mcp-server-linear"
      ],
      "env": {
        "LINEAR_ACCESS_TOKEN": "your_linear_api_token_here"
      }
    }
  },
  "company1-linear": {
    "command": "npx",
    "args": [
      "mcp-server-linear"
    ],
    "env": {
      "LINEAR_ACCESS_TOKEN": "your_company1_linear_token_here",
      "TOOL_PREFIX": "company1"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dvcrn
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