Linear MCP Server
Related Servers
Alternatives to Linear MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server connecting Claude to Linear for searching, creating, updating, and commenting on issues, teams, and projects.210 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Linear's issue tracking system, including creating, updating, searching issues, adding comments, and accessing resources via the Linear API.481 npmMIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables Claude to interact with Linear via a single tool with seven actions: search, get, update, comment, create, graphql, and help.446 npm89MIT
- AlicenseNot gradedqualityDmaintenanceAllows LLMs to integrate with Linear's issue tracking system, enabling them to create, update, search, and comment on issues through the Linear API.481 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for integrating Linear with Claude Code and other MCP clients. Enables issue management, project planning, and status tracking through a set of tools.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Linear that enables creating, searching, updating, and commenting on issues, as well as accessing issues, teams, and user data. Integrates with Claude Desktop and other MCP clients.MIT
TDQS
Scored across 6 tools
Each tool has a distinct purpose: fetching a specific ticket, listing assigned issues, adding comments, creating issues, listing teams, and searching. The only potential overlap is between get_my_issues and search_issues, but the descriptions clearly separate the convenient personal view from general-purpose search.
All tool names follow a consistent verb_noun pattern with snake_case, such as get_ticket, add_comment, and create_issue. The verbs are varied but appropriate, and the naming style is uniform throughout.
With 6 tools, the server is well-scoped for its purpose. It includes the key operations for reading, creating, searching, and commenting on issues, plus team listing, without unnecessary bloat or missing core basics.
The server covers core read and create operations, comments, and search, but lacks update and delete for issues. This leaves a notable gap in the issue lifecycle, as agents cannot modify or close tickets, making it incomplete for comprehensive Linear workflow coverage.