Skip to main content
Glama
dvcrn

Linear MCP Server

by dvcrn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Linear MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      210 npm
      134
      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.
      1 npm
      MIT

    • 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.
      687 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
      210 npm
      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

    B3.2/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., issue, comment, project, milestone, team, user). There is no overlap; even comment actions (create, delete, resolve, unresolve, update) are clearly separated.

    Naming Consistency5/5

    All tools follow the pattern 'linear_<verb>_<resource>' with underscores and lowercase. Verbs like create, get, list, search, update, delete are used consistently. The naming is predictable and unambiguous.

    Tool Count4/5

    24 tools is a bit above the typical 3-15 range but still reasonable for a project management server covering multiple entities (issues, comments, projects, milestones). It feels slightly heavy but not excessive.

    Completeness4/5

    Core CRUD for issues, comments, and milestones is covered. However, missing update/delete for projects and a dedicated get comment tool (comments are only accessible via get_issue) are minor gaps that agents can work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources