Skip to main content
Glama
atlassian-marketplace-mcp

atlassian-marketplace-mcp

Related Servers

Alternatives to atlassian-marketplace-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients like Claude and Cursor to read and act on Instagram, Facebook, WhatsApp and SMS inboxes, contacts, appointments, flows, comment automation, Content Studio posts, market intel and a knowledge base through the ChatGenius REST API. Exposes 105 scope-capped tools, with destructive actions marked for client approval and idempotency keys guarding every write.
      105
      381 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and invoke tools generated from existing OpenAPI-described REST APIs through a governed MCP gateway with centralized authentication, policy-based access control, rate limiting, PII redaction, auditing, and token-efficient progressive discovery.
      MIT

    TDQS

    B3.4/5.0

    Scored across 95 tools

    Disambiguation4/5

    Most tools have distinct purposes, but the large number (95) and a few aliases (e.g., transactions_aggregate_by_hosting) create minor ambiguity. Overall, the tool set is well-organized, but some reporting tools could be confused without careful reading of descriptions.

    Naming Consistency4/5

    The naming convention is predominantly underscore_case with a resource_action pattern (e.g., app_listing_get, developer_space_member_add). However, there are deviations like 'apps_known' and 'free_starter_tier_export' that break the pattern, and some tools use 'by' in the middle. Overall, it's fairly consistent.

    Tool Count2/5

    With 95 tools, the server is extremely large. While it covers many endpoints, the typical well-scoped server has 3-15 tools. This sheer number makes it difficult for an agent to navigate and select the right tool, even with good descriptions.

    Completeness3/5

    The tool set covers major areas like app listing, app software, versions, developers, promotions, and reporting. However, notable CRUD operations are missing: there is no delete tool for app listings, app software, versions, or tokens. This leaves gaps that could cause agent failures in lifecycle management.