Linear MCP Server vs SQLite MCP Server

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

	Linear MCP Server MCP Servers	SQLite MCP 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 for querying and analyzing SQLite databases through Claude and other MCP clients.
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 / open source (MIT). No usage fees; runs locally against a SQLite file you control.
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	Ad-hoc SQL exploration of a local SQLite database from Claude DesktopPrototyping agentic business-intelligence workflowsTeaching an LLM to write SQL against an introspected schemaBuilding a running insights memo across a multi-turn analysis sessionReference implementation for authoring a custom MCP serverWiring a local SQLite cache into a larger MCP-based agent stackQuick schema documentation via `list_tables` and `describe_table`Lightweight data prep and table creation inside a chat session
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	Zero-config local database access for any MCP client — point it at a .db file and Claude can query, schema-introspect and write immediately. Clean, minimal tool surface (six tools) that maps cleanly to how an LLM actually reasons about a database. Novel `append_insight` + `memo://insights` pattern gives the model a persistent scratchpad for multi-turn analysis. MIT-licensed and open source, so it doubles as a canonical example for building your own MCP server. Multiple install paths — uv, Docker, VS Code one-click — cover most developer setups. No API keys, no cloud, no per-query cost; everything runs on your machine against a file you own.
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	Repository was archived on 29 May 2025 — no more upstream fixes, security patches or new features. Exposes `write_query` and `create_table` to the model, so a careless prompt can mutate or drop data; there is no built-in read-only mode or row-level safety. SQLite-only — no Postgres, MySQL, DuckDB or cloud-warehouse support; you need a different MCP server for those. No authentication, quota or audit layer; intended for local single-user use, not shared/multi-tenant deployments. Insight-memo state lives in the running server process, so it does not survive restarts or multiple concurrent clients cleanly.
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 SQLite MCP Server if

✅ Zero-config local database access for any MCP client — point it at a .db file and Claude can query, schema-introspect and write immediately.
✅ Clean, minimal tool surface (six tools) that maps cleanly to how an LLM actually reasons about a database.
✅ Novel `append_insight` + `memo://insights` pattern gives the model a persistent scratchpad for multi-turn analysis.
✅ MIT-licensed and open source, so it doubles as a canonical example for building your own MCP server.

Compare a different pair →