Skip to main content
Glama
Sign In
atlassian-mcp

atlassian-mcp

by stubbedev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to atlassian-mcp

No user-submitted related servers found.

    Related Servers

    • bitbucket-server-mcp

      Upendrasengar
      A
      license
      A
      quality
      D
      maintenance
      Enables to interact with Bitbucket Server repositories, pull requests, and code reviews, including file browsing, PR management, and review actions through natural language.
      59
      10 npm
      Apache 2.0

    • jira-mcp-server

      TTranchese
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with self-hosted Jira instances via Personal Access Token, supporting issue management and project operations through natural language.
      1,650 npm
      Apache 2.0

    • mcp-server-atlassian-bitbucket

      Deborahw097
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Bitbucket Cloud workspaces, repositories, branches, commits, and pull requests through generic GET, POST, PUT, PATCH, DELETE, and clone tools, including reading PR diffs, adding comments, approving, merging, and filtering responses with JMESPath. It connects LLMs directly to version control workflows so tasks like code review, repository search, and PR management can be done in natural language.
      MIT

    • MCP Jira Server

      apo100l
      A
      license
      A
      quality
      C
      maintenance
      Enables natural-language interaction with self-hosted Jira through the Jira REST API, supporting PAT or browser-cookie/SSO authentication. It allows viewing and managing issues, projects, comments, assignments, and statuses, as well as JQL search and issue creation/deletion.
      12
      62 npm
      MIT
    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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation2/5

    git_get_context and get_dev_context both claim to be the master entry point for coding/review tasks and return heavily overlapping git+Jira status information, making it unclear which one to call. jira_comment also duplicates the comment capability already bundled inside jira_mutate, further blurring tool boundaries.

    Naming Consistency3/5

    Most Jira tools follow a readable jira_<verb_or_noun> pattern and Git tools use git_get_*, but get_dev_context and start_work break the prefix convention, and jira_mutate uses a vague verb instead of a concrete resource-action name. The naming is still mostly predictable despite these deviations.

    Tool Count4/5

    10 tools is a reasonable size for a combined Jira/Git workflow and covers the major operations without feeling bloated. The count is slightly higher than needed because of overlapping entry-point tools and duplicated comment functionality, but it is still well within an appropriate range.

    Completeness4/5

    The set covers core Jira lifecycle operations, attachment retrieval, version management, git context, and diff inspection. Notable gaps include PR creation/merging despite those actions being hinted at in descriptions, and no explicit issue deletion, but most workflows can be completed with the existing tools.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources