linear-mcp
Related Servers
Alternatives to linear-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server for managing Linear issues, projects, teams, and milestones through the Model Context Protocol. It enables users to create, update, and list workspace resources including issue statuses, comments, and user details.17 npmISC
- AlicenseBqualityFmaintenanceMCP server for accessing and managing Linear resources like issues, projects, and comments with full CRUD operations and search.2154 npm1MIT
- 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
- AlicenseNot gradedqualityDmaintenanceMCP server providing tools to manage Linear projects and issues, including creation, listing, viewing details, and deletion, as well as team and user info retrieval.276 npmMIT
- AlicenseNot gradedqualityBmaintenanceCustom MCP server for Linear that enables managing issues, projects, and workspaces through natural language, backed by raw GraphQL.276 npmMIT
- AlicenseNot gradedqualityDmaintenanceCache-first MCP server for Linear that provides tools to search, read, create, update, and comment on issues and projects, caching data locally to reduce API calls and respect rate limits.1MIT
TDQS
Scored across 57 tools
Tools like list_issues, search_issues, and semantic_search have overlapping purposes despite different mechanisms. Similarly, get_issue_status duplicates get_issue's state info, and the many save_* tools could confuse agents. Descriptions help but the sheer number causes ambiguity.
Most tools follow a verb_noun pattern (e.g., list_issues, save_issue), with minor deviations like get_issue_status and link_url_to_issue. The use of save_ for create/update is consistent, but some names like list_issue_labels are slightly inconsistent.
57 tools is excessive for a single MCP server, even for a feature-rich platform like Linear. Many tools could be merged or streamlined (e.g., multiple search variants, separate create/update tools), leading to agent decision fatigue.
The tool set covers most Linear concepts: issues, projects, comments, documents, webhooks, notifications, attachments, relations, and agent sessions. Missing CRUD for teams, users, cycles, and workflow states, but these are less critical for typical workflows.