runelay+AtlassianIntegration · OAuth login
Atlassian on Runelay, an open source MCP gateway
Connect Atlassian once. Claude Code, Cursor, Codex and Grok all use that connection, and the credential never leaves your server.
What this connection does
Jira and Confluence in one place. Runelay connects to the Atlassian remote MCP server at https://mcp.atlassian.com/v1/mcp and puts its tools behind your own endpoint.
Agents find them with search_tools and run them with call_tool, so the Atlassian tool list is not loaded into context until it is needed.
Connect Atlassian
Open the connectors in the panel
Pick Atlassian from the catalog.
Log in once
A browser tab opens on Atlassian. Approve the access and close it.
Done
The token is stored encrypted on your server and refreshed by Runelay. Every agent with a Runelay key can use the connection.
Use Atlassian in your agents
Agents do not need a Atlassian entry of their own. Point each one at Runelay and Atlassian is there.
Questions
Does my Atlassian credential reach the agent?
No. It stays on your Runelay server, encrypted with AES-256-GCM using your RUNELAY_SECRET. Agents only hold their Runelay key.
Do I connect Atlassian once per agent?
No. You connect it once in Runelay, and every agent that points at your endpoint uses the same connection.
I already have Atlassian set up in an agent. Can I bring it?
Yes. runelay migrate reads the MCP servers your agents already have. If the CLI can read the token it arrives connected; otherwise it waits in the reconnect queue in the panel.