Linear MCP Server

Created By
emmett-deena year ago
Connect Claude to Linear project management systems. Retrieve, create, and manage issues and projects seamlessly.
Overview

what is Linear MCP Server?

Linear MCP Server is a Model Context Protocol (MCP) server implementation that connects AI assistants like Claude to Linear project management systems, allowing seamless interaction with project data.

how to use Linear MCP Server?

To use the Linear MCP Server, install it via Smithery or manually configure it with your Linear API key, and then run the server to interact with Linear's GraphQL API.

key features of Linear MCP Server?

  • Access to Linear's GraphQL API through MCP tools
  • Authentication via Linear API key
  • Retrieve, create, and manage issues and projects
  • Comprehensive documentation of available tools

use cases of Linear MCP Server?

  1. Automating project management tasks with AI assistance.
  2. Creating and updating issues directly from an AI interface.
  3. Managing project data efficiently through voice or text commands.

FAQ from Linear MCP Server?

  • Can I use Linear MCP Server with any AI assistant?

Yes! It is designed to work with Claude and potentially other AI assistants.

  • Is there a cost to use Linear MCP Server?

The server is open-source and free to use.

  • What are the prerequisites for installation?

You need Node.js, NPM or Yarn, and a Linear API token.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
emmett-deen
Star
1
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago