Skip to main content
Glama
Sign In
ticket-ai

ticket-ai

by syrian963
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ticket-ai

No user-submitted related servers found.

    Related Servers

    • engineering-standards

      rajgurung
      A
      license
      A
      quality
      D
      maintenance
      Enforces team engineering standards across Git, code review, Rails, frontend, deployment, incidents, observability, API design, database, ADRs, and technical debt, with tools for branch name and commit message validation.
      4
      MIT
    • Tently MCP

      Tently MCPofficial

      tently-team
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents such as Claude Code and Cursor to check a team's learned decisions from pull requests, reviews, and docs before writing code, showing whether breaking them is blocking or advisory. It also provides locally computed symbol impact/blast-radius analysis so source code never leaves the machine.
      55 npm
      2
      MIT

    • mcp-zen-of-languages

      Anselmoo
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and developers to analyze code for language-specific best practices and idiomatic patterns across programming languages, CI automation, and configuration formats.
      16
      2
      MIT

    • jira-work-logger

      AbdAlrahmanAlQaroot
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI coding agent to scan a day's git commits across work repositories and group them into Jira tickets, creating or updating them with estimates and logged time. It also surfaces actionable, categorized errors so an agent knows what failed and whether to retry.
      MIT

    • devcontract

      maazbin
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve cited git-history explanations for files and tickets, compile a Team Engineering Contract from repository artifacts, and follow guided Understand/Build workflows over MCP stdio. It lets clients such as Grok, Claude Code, Codex, Kiro, and Cursor share the same tools for evidence-backed repository understanding.
      1
      1 npm
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: house_style and learn_conventions are related but house_style reads the cache while learn_conventions populates it, which is well-communicated. review_ticket and review_draft are similar but review_draft explicitly targets unpublished drafts)Skip, so they are distinguishable. template_gaps and ticket_template serve different functions (gap analysis vs skeleton). The one potential confusion is review_ticket and review_draft, but the descriptions clearly differentiate them.

    Naming Consistency3/5

    Most tools follow a noun_action pattern (e.g., learn_conventions, review_ticket, review_open_tickets), but there are inconsistent verb placements and some names are less clear: house_style is a noun phrase, ticket_template is a noun phrase, and template_gaps is a noun phrase without a verb. This mixes patterns (verb-first vs noun-first) and some names are not imperative verbs, which is inconsistent.

    Tool Count5/5

    With 8 tools, the count is well within the ideal 3-15 range. Each tool has a specific role in the ticket lifecycle: learning conventions, retrieving templates, gathering context, reviewing drafts, reviewing created tickets, and reviewing the open board. No tool feels redundant, and the set is tightly scoped to the server's purpose of ticket style analysis and validation.

    Completeness5/5

    The tool set covers the full lifecycle: learning conventions (learn_conventions, house_style), generating templates (ticket_template), gathering context (ticket_context), checking gaps (template_gaps), and reviewing both drafts and existing tickets (review_draft, review_ticket), plus batch review (review_open_tickets). There are no obvious missing operations for the stated purpose; if anything, the coverage is thorough.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources