Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Linear's MCP server matches the product's personality: hosted, fast, and requiring approximately zero setup. Add mcp.linear.app to your client, approve the OAuth prompt, and your assistant can find and create issues, update statuses and assignees, comment, and work with projects, cycles and labels.
The friction it removes is small per instance and large in aggregate. Filing a well-formed bug — clear title, reproduction steps, right team, right labels — takes a minute of form-filling in the app; in conversation it's "file this as a bug on the API team" while the context is still warm. Standup prep ("what's assigned to me this cycle and what did I move yesterday?"), triage sweeps ("show unassigned urgent issues across teams"), and status narration ("summarise the auth project's progress for the exec update") all become single requests.
The deeper shift is where issues come from. When your coding assistant hits a bug mid-session, it can file the issue itself — stack trace, context, suspected cause — without you switching tools. Code review comments become tracked follow-ups instead of vibes. The tracker starts reflecting reality more completely because capture stops competing with flow.
Linear was one of the first majors to ship an official hosted MCP server, and the OAuth model means credentials never touch your config files — access rides your Linear login and can be revoked there. Actions happen as you, so your client's tool confirmations are the guardrail for creation and edits. If your team lives in Linear, this is about as close to a no-brainer as MCP integrations get.
ENG-142) rather than title; lookups resolve it directly and skip the ambiguity of two issues named "flaky test".Issues filed from the coding session with the context still attached.
Unassigned/urgent sweeps and bulk status questions answered instantly.
Project progress summarised from real issue states, not memory.
| Tool | What it does |
|---|---|
| list_issues / get_issue | Find and read issues with filters (team, assignee, state) |
| create_issue | File issues with title, description, team, labels and priority |
| update_issue | Change status, assignee, estimates and fields |
| create_comment | Comment on issues |
| list_projects / get_project | Read project state and progress |
| list_cycles | Work with cycles/sprints |
| list_teams / list_users | Resolve teams and teammates |
claude mcp add --transport http linear https://mcp.linear.app/mcpOAuth prompt opens in the browser on first use.
A Linear account. Nothing to install for HTTP-capable clients; OAuth handles auth and revocation.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
Feed real design data to your coding assistant — layout, tokens and components straight from Figma files.