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.
      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.
      280 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
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, but set_state and comment both can carry description patches, creating a slight overlap. claim and check_claim are complementary yet clearly separated by intent and timing. Overall, an agent can usually tell them apart from descriptions.

    Naming Consistency4/5

    Names are mostly snake_case and follow verb_noun for actions (set_state, list_issues, create_issue), but noun phrases like description_history and notifications, plus standalone verbs like claim and comment, break the pattern. Still readable and predictable within tool categories.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 range, but the server's strict, multi-step workflow justifies each tool with a distinct operation. No obvious redundancy; borderline heavy but reasonable for this domain.

    Completeness4/5

    The surface covers ticket creation, reading, description state changes, comments, fields, status, claims, notifications, and supporting lists. Missing delete ticket and comment editing operations, but the core agent lifecycle is complete with workarounds for minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources