Linear MCP Server vs MCP Git Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Linear MCP Server MCP Servers	MCP Git Server MCP Servers
Tagline	Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)	Reference MCP server that lets any LLM read, search, and manipulate local Git repositories.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Requires a Linear account and personal API key; Linear itself is free for small teams, $8/user/mo Standard, $14/user/mo Plus.	Free· Free and open source (MIT License). Self-hosted; you pay only for the compute wherever you run it.
Model	—	—
Editorial score	—	—
Use cases	Filing bugs from Claude Desktop or Cursor without leaving the editorAgent-driven triage of the inbox projectBulk relabeling or reprioritising issues via natural languageStandup summaries of a user's assigned Linear workAdding comments to tickets from a coding agent's PR reviewReference implementation for building a custom Linear MCP server	AI-drafted commit messages from staged diffsAssistant-led code review of unstaged changesWalking git log and git show to find a regressionCreating and checking out scratch branches from chatSummarising what changed between two refsStaging or resetting files during a refactor sessionReference implementation for building custom MCP serversLocal repo introspection inside Claude Desktop or Cursor
Pros	Open source (MIT) and small enough to read end-to-end in an afternoon One-line install via Smithery or straight npx in Claude Desktop config Covers the create / update / search / comment loop that 90% of ticket workflows need Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents) Clear tool schemas make it a good reference implementation for building your own MCP servers Uses Linear's official GraphQL API, so permissions and audit trails stay intact	Official reference implementation maintained in the modelcontextprotocol/servers monorepo, so it tracks the spec closely and is a safe example to copy. Covers the everyday Git verbs an assistant actually needs (status, diff, log, show, add, reset, commit, branch, checkout, init) in one small binary. Runs fully local against a repo_path you control, so source code and .git history never leave your machine. Trivial to install (pip install mcp-server-git or uvx mcp-server-git) and to wire into Claude Desktop, VS Code, Cursor, or any MCP host with a few lines of JSON. MIT-licensed and open source, easy to fork if you want to add extra subcommands or tighten permissions. Composes cleanly with other MCP servers (filesystem, shell, GitHub) rather than trying to be a monolithic dev-agent.
Cons	Officially deprecated by its author in favour of Linear's own remote MCP server at mcp.linear.app/sse Runs as a local stdio process, so it has to be installed on every workstation and cannot be shared across a team Uses a personal API key, meaning every action shows up as the key owner rather than the actual LLM user Tool coverage is narrower than the official server: no cycles, projects, roadmaps, or workflow state management Error handling and rate-limit backoff are minimal; heavy agent loops can trip Linear's API limits	Scope is intentionally narrow: no push/pull/fetch, no merge, rebase, stash, cherry-pick, tag, or submodule support. Does not talk to GitHub/GitLab/Bitbucket APIs; PRs, issues, and code review still need a separate server such as github-mcp-server. Marked as early development in the README, so tool names and argument shapes can shift between releases. No built-in authorisation model - if the LLM can call git_commit or git_reset it can rewrite your working tree, so you rely on the host client's approval prompts. Python runtime requirement (uv/pip) is an extra dependency compared with the single-binary Go/Node MCP servers some teams prefer.
Website	github.com	github.com

Pick Linear MCP Server if

✅ Open source (MIT) and small enough to read end-to-end in an afternoon
✅ One-line install via Smithery or straight npx in Claude Desktop config
✅ Covers the create / update / search / comment loop that 90% of ticket workflows need
✅ Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)

Pick MCP Git Server if

✅ Official reference implementation maintained in the modelcontextprotocol/servers monorepo, so it tracks the spec closely and is a safe example to copy.
✅ Covers the everyday Git verbs an assistant actually needs (status, diff, log, show, add, reset, commit, branch, checkout, init) in one small binary.
✅ Runs fully local against a repo_path you control, so source code and .git history never leave your machine.
✅ Trivial to install (pip install mcp-server-git or uvx mcp-server-git) and to wire into Claude Desktop, VS Code, Cursor, or any MCP host with a few lines of JSON.

Compare a different pair →