Skip to main content
Glama
tiovikram

Linear MCP Server

by tiovikram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Linear MCP Server

No user-submitted related servers found.

    Related Servers

    • Linear MCP Server

      packetnomad
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Linear's issue tracking system through a standardized Model Context Protocol interface, allowing users to create, update, search, and manage issues, projects, and comments via natural language.
      210 npm
      1
      MIT

    • Linear MCP Server

      samcfinan
      A
      license
      Not graded
      quality
      D
      maintenance
      Facilitates project management with the Linear API via the Model Context Protocol, allowing users to manage initiatives, projects, issues, and their relationships through features like creation, viewing, updating, and prioritization.
      481 npm
      6
      MIT

    • Linear MCP Integration Server

      skspade
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to interact with Linear for issue tracking and project management through the Model Context Protocol, supporting capabilities like creating issues, searching, managing sprints, and bulk updating statuses.
      5
      -
    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 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific resource (issue, project, team) and action (create, get, list, search, update), making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_issue, list_issues, update_issue). The naming is uniform and predictable throughout the set, with no deviations in style or convention.

    Tool Count5/5

    With 7 tools, the count is well-scoped and appropriate for a Linear issue management server. Each tool earns its place by covering essential operations without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong CRUD coverage for issues (create, get, list, search, update) and lists for projects and teams. A minor gap exists in missing delete operations for issues, projects, or teams, but agents can still handle core workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources