Skip to main content
Glama

Related Servers

Alternatives to Linear

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that integrates with Linear's API, enabling users to manage issues, projects, teams, and comments through natural language. It supports creating, updating, deleting, and searching issues, as well as project and team management.
      25
      2,020 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that enables interaction with Linear.app's API for issue tracking, project management, and workflow automation. It allows users to create, update, and search issues, manage cycles and labels, and perform team operations through natural language.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server for the Linear API, enabling AI assistants to list, inspect, and create issues, as well as manage teams and projects through controlled tools.
      313 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Linear project management systems, allowing users to create, update, and manage issues, projects, teams, and comments through natural language.
      41,337 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Custom MCP server for Linear that enables managing issues, projects, and workspaces through natural language, backed by raw GraphQL.
      82 npm
      1
      MIT

    TDQS

    C2.8/5.0

    Scored across 198 tools

    Disambiguation3/5

    Most tools pair a distinct entity with an action, but the 198-tool surface contains many overlapping list/search variants such as getIssues, searchIssues, getProjectIssues, and getCycleIssues. Archive/delete/remove/unarchive distinctions also require careful reading, so selection errors remain likely despite helpful descriptions.

    Naming Consistency4/5

    Names consistently use the linear_ prefix followed by camelCase verb+entity patterns, with predictable get/create/update/archive/delete forms. Minor deviations such as getViewer and getOrganization versus plural list names like getUsers are readable but not perfectly uniform.

    Tool Count1/5

    198 tools is far beyond a well-scoped MCP server and creates an extreme selection and maintenance burden. Even for a large domain like Linear, the surface should be split, tiered, or reduced to core workflows.

    Completeness4/5

    Coverage is extensive across issues, projects, cycles, initiatives, documents, releases, customers, webhooks, OAuth, notifications, and admin surfaces. However, there are notable gaps such as no unarchiveIssue/deleteIssue, limited label CRUD, no obvious listIssueRelations, and several resources supporting archive but not full delete/unarchive lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive