Feature request to add issue-properties write to Atlassian MCP server

[Eleni Konior]

We're looking for a simple way to handle writes to issue properties through the Atlassian MCP server. The alternatives require a lot of overhead to avoid per-developer setup (e.g., Jira API tokens). Our engineers already heavily use the Atlassian MCP server (thank you!), so we're hoping to add one more tool or a wrapper tool that can handle various API operations perhaps?

We're also open to contributing to the repo: https://github.com/atlassian/atlassian-mcp-server but would want to know if this aligns with the team's (Atlassian's) roadmap. I don't see anything in the GitHub issues referencing issue properties.

[Tomislav Tobijas]

Hi @Eleni Konior ,

There's no official/public roadmap when it comes to MCP development. I've looked for a bit in JAC if there are any mentions of using issue/work item properties, but nothing did pop out. 👀

I'm guessing you've tried using methods and endpoints related to Issue properties and that this isn't supported with MCP? (I haven't tested that part, so that's why I'm asking) 🤔

Meanwhile, you or your app admin can probably reach out to Atlassian Support to see if they will provide some additional insights that could be related to your requirements.

Btw, I'm going to move this to the Rovo forum group - someone might chime in with some additional info.
Also, when talking about MCP, there's a dedicated forum discussion group related to that: Atlassian Rovo MCP Server 

Cheers,
Tobi