Skip to main content
Glama
arucil

dsh-linear-mcp

by arucil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to dsh-linear-mcp

No user-submitted related servers found.

    Related Servers

    • 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-mcp

      adelaidasofia
      A
      license
      B
      quality
      A
      maintenance
      Multi-workspace Linear MCP server using Personal API Keys instead of OAuth. Provides tools for managing issues, projects, teams, and more across multiple workspaces.
      57
      1
      MIT

    • mcp-linear

      pius-grainger
      F
      license
      A
      quality
      B
      maintenance
      Enables 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
      -

    • Linear MCP Server

      Iwark
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Linear resources through an MCP interface, offering functionality for issue management and resource retrieval with rate limiting and error handling support.
      1,314 npm
      1
      MIT

    • MCP Linear.app Server

      MoshPitLabs
      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.
      -
    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

    B3.4/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. The three issue listing tools (search, list, list_my) have clear differences: full-text search, filterable list, and self-assigned list. All other tools (comments, relations, entities) are mutually exclusive.

    Naming Consistency5/5

    All tools follow the uniform pattern 'linear_<verb>_<noun>' with snake_case. Verbs are consistent (get, list, create, update, delete, add, search, archive) and nouns are clear. No mixed conventions or vague verbs.

    Tool Count4/5

    At 22 tools, the count is slightly above the typical 3-15 range but not excessive. The size is justified by the breadth of Linear entities (issues, comments, relations, teams, users, projects, cycles, labels, workflow states) and the comprehensive issue lifecycle coverage. It feels a bit heavy but each tool serves a distinct purpose.

    Completeness4/5

    Issue management is fully covered with create, read (get/list/search), update, archive, and delete. Comments and relations have complete CRUD-like coverage. However, non-issue entities (teams, users, projects, cycles, labels, workflow states) only have list operations, lacking get/create/update/delete. This is a minor gap given the server's apparent issue-centric focus.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources