Linear
Related Servers
Alternatives to Linear
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI tools like Cline to manage Linear issues, projects, and teams via the Linear API.241,466 npm2MIT
- FlicenseAqualityBmaintenanceEnables reading and managing Linear issues by human-readable ID, with tools for searching, creating, updating, commenting, and resolving teams, states, labels, and assignees by name.11-
- 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.788 npmMIT
- AlicenseBqualityDmaintenanceEnables interaction with Linear's API to manage issues, projects, and teams. Supports creating, updating, searching, and deleting issues, along with project management and team operations through API key authentication.13280 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Linear workspaces by listing, retrieving, creating, and searching issues, and listing teams via the Linear GraphQL API.2 npmMIT
- 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.788 npmMIT
TDQS
Scored across 22 tools
Most tools are clearly distinct by resource and action (e.g., issues vs. projects vs. milestones). The few potentially confusable pairs are singular/plural variants like create_issue/create_issues and delete_issue/delete_issues, but the plural forms clearly indicate bulk operations.
All tools use a consistent linear_ prefix followed by snake_case verb_noun patterns (e.g., create_issue, search_projects, get_project_milestones). The singular/plural distinction is applied uniformly, and there are no mixed conventions or vague verbs.
At 22 tools, the count falls into the borderline-heavy range (16-25). However, the coverage spans multiple subdomains (issues, projects, milestones, comments, auth, teams, user), so the count is defensible but feels slightly high for an MCP server.
Issues have create, update (bulk), delete, and search, but no single-issue get; projects support create/get/search but not update or delete; comments only support get and create. These are notable gaps in lifecycle coverage for the core resources.