Skip to main content
Glama

Related Servers

Alternatives to jira-ai-auditor

  • A
    license
    A
    quality
    D
    maintenance
    Tamper-evident audit logging for AI decisions. Three tools (record_decision, verify_decision, list_decisions) write to a regulator-grade ledger built on AWS S3 Object Lock with 7-year retention. Designed for EU AI Act Article 12 and FCA SS1/23 evidence requirements. Try zero-config: npx audit-ledger-mcp boots in sandbox mode against a public hosted tenant.
    3
    57 npm
    1
    Apache 2.0
  • F
    license
    A
    quality
    C
    maintenance
    An async MCP server for JIRA integration, enabling AI assistants to search, create, and manage JIRA issues via JQL and other operations.
    6
    2
    -

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables natural language interaction with Jira for managing projects, issues, tasks, and workflows through the Model Context Protocol, allowing users to delegate PM tasks through Claude Desktop.
    27 npm
    64
    MIT
  • A
    license
    C
    quality
    D
    maintenance
    Connects Jira with Claude, enabling users to search issues, view issue details, update issues, add comments, and retrieve project information through natural language commands.
    1
    78 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Connects AI assistants like Claude to Jira projects, enabling natural language queries and operations for issue management, project tracking, comments, and workflows through the Jira REST API.
    14,527 npm
    77
    ISC
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.
    441 npm
    2
    MIT

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

audit_project and audit_sprint target clearly distinct scopes (whole project vs. individual sprint), so an agent can always pick the right one. No overlapping purpose exists between the two tools.

Naming Consistency5/5

Both names follow an identical verb_noun snake_case pattern (audit_*), directly mirroring the two domain objects. There is no deviation or mixed convention.

Tool Count3/5

Two tools is thin for a server positioning itself as an enterprise-grade auditing suite; the surface feels narrow even for a deliberately focused auditor. It is not egregious, but it sits at the low end of usefulness.

Completeness3/5

Project-level and sprint-level auditing are covered, but obvious adjacent operations are absent — e.g. issue/task-level audit, backlog or board analysis, historical trend reporting, or exporting audit results. Agents will hit dead ends for anything outside those two scopes, and the 'Premium' gating on half the surface further narrows coverage.

Maintenance

ActivityMaintained
ResponsivenessNo issues