Skip to main content
Glama
pius-grainger

mcp-linear

by pius-grainger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-linear

No user-submitted related servers found.

    Related Servers

    • Linear MCP Server

      veddnd
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with Linear's issue tracking system, including creating, updating, searching issues, adding comments, and accessing resources via the Linear API.
      1,314 npm
      MIT

    • Linear MCP Server

      timottowitz
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      13
      586 npm
      MIT

    • linear

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Linear workspaces by listing, retrieving, creating, and searching issues, and listing teams via the Linear GraphQL API.
      5 npm
      MIT

    • Linear

      cline
      A
      license
      B
      quality
      C
      maintenance
      Enables managing Linear issues, projects, and teams through Cline. Supports CRUD operations, bulk actions, and rich text descriptions.
      22
      586 npm
      134
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: list_* clearly separates teams, states, labels, users, and my issues, while get_issue, search_issues, and list_my_issues offer different retrieval modes. Comments, creation, and updates are also cleanly separated with no overlapping responsibilities.

    Naming Consistency5/5

    The tools consistently follow a verb_noun snake_case pattern: list_teams, list_states, get_issue, create_issue, update_issue, add_comment, and so on. list_my_issues is a minor variation but still predictable and fits the overall naming logic.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a Linear issue-management integration. It provides reference lookups, issue operations, and comments without redundant or unnecessary tools.

    Completeness4/5

    The core issue lifecycle is covered: create, get, update, search, list-my-issues, and comments, plus supporting lookups for teams, states, labels, and users. Obvious gaps like deleting/archiving issues or listing all issues in a team are minor and can often be worked around with search_issues.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources