Hi @Edith Kuhn, first thing I would look at is which URL your mcp.json points at. If it is https://mcp.atlassian.com/v1/mcp/preview, this is expected rather than broken. Atlassian's v2 preview announcement from 1 July puts "Dozens of new tools abstracted behind discover and execute tools" and gives you "Reduced default tool exposure", so the Jira write tools are not offered by name on that endpoint at all. The OAuth page points custom clients at /v1/mcp/authv2 instead, and on that one the write_jira group comes back: createJiraIssue, editJiraIssue, transitionJiraIssue, addCommentToJiraIssue, addWorklogToJiraIssue.
If you are already on authv2 and the tools are listed while the calls fail, that is a different thing. Read the error. An org-level block gives you this one word for word: "Access denied: Your organization admin has not authorized the write permission." That one is an org admin's to clear, if it isn't you. Atlassian Administration, then Rovo, then Rovo MCP server, then the Permissions tab, and set Write back to Allowed. Takes effect immediately, no reconnect. The bit that gets missed there is that a Jira-only block leaves the Write row reading Partially allowed, so it glances as fine.
Nothing changed on their side for everyone in the last day or so, as far as I can check from outside. The rovo-mcp changelog holds two entries, the v2 preview and the April auth-server move, and the metadata on authv2 still advertises write:jira-work. Neither of those would show a change made inside your own org.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.