Is this project dead?

[khalidyousif-smtc]

Not sure what's going on... but the maintainer went radio silent over a month ago and their last code commit was on Jun 29...

I hope that they are on an extended vacation or something...

[jtumidanski]

It's dead Jim

[SharkyND]

@khalidyousif-smtc @jtumidanski I sense the same too, should we fork this project and have some discussion around it?

[SharkyND]

https://github.com/SharkyND/mcp-atlassian

Added a few features and a helm chart, if you guys wanna check out

[mliq]

I also forked it with a major bug fix (started by @4erdenko) and improved error messaging at https://github.com/mliq/mcp-atlassian

(PR here if the owner returns: #690)

[nealedj]

Definitely seems dead. Is anybody serious about picking this up and maintaining it? There are plenty of outstanding issues and PRs in this project that could do with being migrated and addressed. @SharkyND and @mliq are either of you willing to take it on?

[SharkyND]

Hey @nealedj , yes for sure. I would love to do that, but I'm not a contributor to this project hence had to fork it and address those changes. I tried emailing @sooperset too on the gmail account but didn't recieve a reply.

I have a few of my friends and collegues there trying to maintain this fork, I will urge all of us in this community that can't use the Atlassian cloud and its cloud offering MCP (https://www.atlassian.com/blog/announcements/remote-mcp-server) to help us maintain this version.

For our version mcp-atlassian we already have or about to add:

• Dynamic Headers that works with SSE/HTTP-Stream - (Done)
• Dynamic and scalable helm chart (Done - we are using it in production at scale)
• Adding Bitbucket tools as a client too - Raised PR - Added bitbucket MCP tools. SharkyND/mcp-atlassian#7

We have a few more ideas and would love if you guys can add it in the discussion there. Also would love if you guys can try it out and help built this with us!

CC: @mliq wanna join forces on this mcp-atlassian

Thanks!

[MarouaneZhani]

Hey @SharkyND,
Thanks for sharing your fork with us!
Since you are not using also the Atlassian Cloud, and you are using this MCP server in production, you might already dealt with User authentication at scale ?
I saw here in the docu that it should be setup like that
{
"mcpServers": {
"mcp-atlassian-service": {
"url": "http://localhost:9000/mcp",
"headers": {
"Authorization": "Token <USER_PERSONAL_ACCESS_TOKEN>"
}
}
}
}
but I couldn't get it running with this, and also not sure which PAT to include (Jira or Confluence).
Do you have any experience with that ?

[SharkyND]

@MarouaneZhani Checkout what we did here: SharkyND/mcp-atlassian#1

Essentially to address this we are using dynamic headers. If you use this version: mcp-atlassian, you can then simply:

    "Atlassian": {
        "url": "http://localhost:8000/mcp",
        "headers": {
            "X-Atlassian-Read-Only-Mode": "true",
            "X-Atlassian-Jira-Personal-Token": "<PAT>",
            "X-Atlassian-Jira-Url": "<Ent. Jira Url>",
            "X-Atlassian-Confluence-Personal-Token": "<PAT>",
            "X-Atlassian-Confluence-Url": "<Ent. Confluence Url>",
        },
        "type": "http"
    }

Let me know if you have questions. Raise any issues if you see there.

Thanks.

[drewagentsync]

I'm going to start using your fork @SharkyND the issues in this one slowed me down significantly (particularly the fix of simply using fastMCP 2.5.0 to fix the lack of usable error output) I'll try to help contribute where I can 👍

[mkjkec2005]

We are also going to use your fork @SharkyND . Could you please help us resolve the issue referenced here?
SharkyND/mcp-atlassian#19

[kyousif87]

There are so many forks that popped out of this repo, I am unsure which one to use anymore :/

[mliq]

@kyousif87 I've continued to use my fork and it has been working very well for me and others on both DC and Cloud JIRAs/Confluences. But it seems like @SharkyND's fork has the most active development ongoing, so you should probably go with that one.

[Troubladore]

@sooperset - Can you address some of these concerns? I'm not sure what the relative state of this repo is relative to the forks, but I see there has been recent activity here. I'm going through the old issues in this repo, but if we can true back up to the changes that have happened along the way, that will make for a more unified experience.

[Troubladore]

For anyone following this thread and wondering about the state of the various forks — I did a thorough comparison of the SharkyND and mliq forks against this project. Here's what I found:

Already in this project (fork work is now redundant):

• Helm chart (helm/ directory)
• Dynamic header-based authentication (UserTokenMiddleware)
• ASGI protocol fixes
• Read-only mode hiding write tools from discovery
• Confluence URL trailing slash fix
• Custom field JSON parsing (mliq/4erdenko's fix) — covered by JSON string validation
• Bearer JWT token handling — _disambiguate_bearer_auth_type() handles this at the dependency layer

Unique to the fork ecosystem (not in this project):

• Bitbucket MCP tools (SharkyND + aakashH242)
• Prometheus observability metrics (SharkyND)
• Xray test management tools for Server/DC (Parshantyaduvanshi1 via SharkyND) [already declined as a feature for this project]
• Entra ID / Azure AD authentication (mtneni via SharkyND)
• Multi-site support — multiple Jira/Confluence instances in one server (ubisoft/mcp-atlassian has a working implementation with factory-based registration and dedicated tests, relevant to Support for multiple Jira/Confluence instances per server process #231)

Small gaps found across multiple forks (nszceta, suparious):

• jira_get_comments — the method exists internally but isn't exposed as an MCP tool
• jira_delete_comment — not implemented at all

We're tracking these and plan to submit PRs for the comment tools.

If you're currently using SharkyND's, mliq's, or ubisoft's forks for any of the features in the first list, this project should cover your needs now. The features in the second list would need to be implemented if there's community interest.