[Feature]: Mode: HTTP access with PATs - Send Confluence AND Jira PATs

[carlhettig]

Is your feature request related to a problem? Please describe.

Hi,

I have the following setup:

• Central MCP server, running as container, accessible via HTTP
• Jira and Confluence running on-premises, both provide PATs (access tokens)
• Works fine in general.

Problem:
In the current mcp.json, I can only provide a single token. Example:

{ "servers": { "mcp-atlassian-confluence": { "url": "http://172.ZZ.YY.XX:3000/mcp", "headers": { "Authorization": "Token XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "Accept": "application/json" } } } }

So far, it’s not clear how to supply both Jira and Confluence PATs when using HTTP mode.
Request:

• Is it possible to configure both Jira and Confluence PATs in one mcp.json?
• If not, could the code be extended to support multiple PATs (e.g., one for Jira, one for Confluence)?

If someone could give me an explanation of the current behavior and possible extension points, I’d be happy to propose or contribute a code change.
Thanks & best regards,
Carl

Describe the solution you'd like

{ "servers": { "mcp-atlassian-confluence": { "url": "http://172.ZZ.YY.XX:3000/mcp", "headers": { "Authorization": "TokenJira XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX TokenConfluence YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY", "Accept": "application/json" } } } }

Describe alternatives you've considered

No response

Use Case

Central MCP server, running as container, accessible via HTTP, Jira and Confluence running on-premises, both provide PATs (access tokens)

Additional Context

No response

[carlhettig]

I found a workaround that may help others with the same problem:

I now run two separate MCP containers – one for Confluence, one for Jira.

In the Confluence container I restrict the available tools using the --enabled-tools argument to only expose Confluence tools, and I pass the Confluence PAT as environment variable.

In the Jira container I do the same, but only enable Jira tools and provide the Jira PAT.

With this setup I can hand over two different tokens cleanly and avoid collisions. It works reliably, although of course it would still be nice if a single MCP instance could handle both PATs directly.