Skip to main content
Glama
justinstimatze

MCP Linear

by justinstimatze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Linear

No user-submitted related servers found.

    Related Servers

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

    • Linear MCP Server

      emmett-deen
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server implementation that enables AI assistants to interact with Linear project management systems, allowing them to create, retrieve, and modify data related to issues, projects, teams, and users.
      14 npm
      3
      MIT

    • 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 Kanban Server

      0xikarus
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables management of Linear kanban boards, projects, and issues directly through Claude via the Model Context Protocol. It includes an automatic task tracking hook that synchronizes Claude's real-time work progress directly to Linear boards.
      -
    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

    C2.9/5.0

    Scored across 198 tools

    Disambiguation3/5

    Many tools follow a clear resource+action pattern, but there are several near-overlapping retrieval families (getIssues/searchIssues/getProjectIssues/getCycleIssues, generic vs entity-scoped document getters, getSavedViews/getFavoriteViews). At 198 tools, an agent will frequently have multiple plausible tools for the same need despite generally clear descriptions.

    Naming Consistency5/5

    All tools share the linear_ prefix followed by a consistent camelCase verb+noun convention (getX, createX, updateX, archiveX, addXToY, removeXFromY, deleteX). Even long names like createOAuthClientCredentialsToken follow the same predictable pattern.

    Tool Count1/5

    198 tools is far beyond the 25+ 'too many' threshold and makes the surface extremely difficult to navigate. Even for a comprehensive Linear integration, this is an extreme mismatch that would be better split into focused domain-specific servers.

    Completeness4/5

    The tool surface is exceptionally broad, covering issues, projects, cycles, initiatives, roadmaps, releases, documents, customers, webhooks, OAuth, notifications, and audit events. Minor gaps exist, such as no direct delete for projects/teams/documents/workflow states, no label update/delete, and no attachment deletion, but core workflows are generally covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources