Connecting n8n using the Atlassian Remote MCP Server

Questions
1

Describe the problem/error/question

Anyone has suggestions on how to connect to Atlassian Remote MCP server using n8n?

What is the error message (if any)?

Please share your workflow

Failed to execute operation: Failed to connect to MCP server: SSE error: Non-200 status code (401)

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:**1.99.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):**Docker
  • **Operating system:**Ubuntu
2

As far as I can see, the official Atlassian Remote MCP Server only supports OAuth 2.0 which isn’t configurable in n8n cloud - Unless I’m missing something?

3

Correct, right now, MCP client supports bearer and generic header authentication

The Atlassian Remote MCP Server requires OAuth 2.1.

1 Like
4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

5

OAuth for the MCP client node was added in 1.119.0, see PR here: feat(MCP Client Tool Node): Add support for OAuth2 with Dynamic Client Registration by RomanDavydchuk · Pull Request #21034 · n8n-io/n8n · GitHub