Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Claude Code Rovo MCP - API Token Authentication Issue

Warren Januel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 15, 2026

Hi,

My Atlassian admin and I are having trouble getting our workflow to work with the Atlassian Rovo MCP using API Token authentication. We’re trying to automate Jira ticket creation through our CI/CD pipeline.

We’ve configured everything according to the documentation:
(https://support.atlassian.com/security-and-access-policies/docs/manage-atlassian-mp3 juice-rovo-mcp-server/)

However, when connecting, Claude only has access to read-only tools. I’m getting the following issue:

Unfortunately, I’m unable to create a Jira ticket. The Atlassian MCP tools available (getTeamworkGraphContext and getTeamworkGraphObject) are read-only — they can fetch and display existing Jira data but cannot create new issues. Attempts to access the Atlassian API return a 401 Unauthorized error, suggesting the MCP integration may not have write permissions configured.

We’ve tried:

  • Using three different API tokens, all with full permissions
  • Removing and re-adding the MCP connection

Nothing seems to enable access to any write tools or permissions. We’re currently stuck.

This is our current MCP configuration:

 

{
"mcpServers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v1/mcp",
"headers": {
"Authorization": "Bearer ${{ secrets.ATLASSIAN_MCP_API_TOKEN }}"
}
}
}
}

Any advice or suggestions on how to properly configure write access for Claude with MCP would be greatly appreciated.

2 answers

1 accepted

0 votes
Answer accepted
Arkadiusz Wroblewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 15, 2026

Hello @Warren Januel 

The issue is the auth format.

Your config uses Authorization: Bearer ..., but that only works for a service account API key. If you are using a normal personal Atlassian API token, the MCP server expects Basic auth instead.

That would also explain the 401 and why you only see a limited set of tools.

So check which credential you are using: a personal API token needs Basic auth, while Bearer is for a service account API key.
Also make sure API token authentication is enabled for the Rovo MCP server on the Atlassian side.

0 votes
Jordi Romera
Contributor
April 15, 2026

Hello Warren :-) 

 

Short question: Are you using Claude Code to create Rovo agents with Forge?

 

Regards,
Jordi

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events