Skip to main content
Glama
justinstimatze

linear-strict

by justinstimatze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to linear-strict

No user-submitted related servers found.

    Related Servers

    • Coordination MCP

      limars874
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI agents to share, incrementally synchronize, and restore work context within a common scope using persistent tickets, immutable updates, and text artifacts.
      MIT

    • rebar-mcp

      navapbc
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to manage an event-sourced, git-backed ticket store through MCP tools, supporting operations like ticket creation, claiming, and transitions.
      54 PyPI
      4
      Apache 2.0

    • Linear MCP Server

      verymbuemo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Linear workspace resources such as issues, projects, teams, cycles, and comments via Streamable HTTP MCP, with LLM-optimized tools and batch operations.
      82 npm
      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
      -

    • Ticket MCP Server

      recursivesquircle
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage a file-backed ticketing system directly within a local repository using a structured state machine and directory hierarchy. It enforces strict markdown schemas and provides specialized tools for claiming tasks, appending work logs, and validating ticket metadata.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 19 tools

    Disambiguation4/5

    The set is largely distinct and even deliberately splits near-twins (mark_notifications_read vs mark_principal_notifications_read, notifications vs get_principal_notifications) with explicit rationale. The one real risk is the set_state / set_status / set_fields triple, which share a prefix and could be mis-picked at a glance, though the descriptions clearly delimit each (content vs workflow state vs other fields).

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (list_issues, create_issue, set_status, mark_notifications_read) with consistent prefixes for related operations. Minor deviations exist (whoami, notifications as a bare noun, claim), but overall the convention is readable and predictable.

    Tool Count4/5

    19 tools sits just above the well-scoped band, but the strict workflow governance (claim, check_claim, set_state, set_status, comment typing, principal-inbox separation) justifies most of them. Few tools appear redundant; the count is slightly heavy rather than bloated.

    Completeness4/5

    Issue lifecycle is well covered (create, read, list, field edits, state transitions, claims, comments, history) plus teams, projects, cycles, initiatives and notifications. Gaps are minor: no delete/archive, no single-team/user lookups, and no global search beyond list_issues filters.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources