Skip to main content
The Atlassian Rovo MCP Server is Atlassian’s hosted MCP server for Jira, Confluence, Jira Service Management, Bitbucket, and Compass. Connect it to Spojit and your workflows can search and create Jira issues, read and update Confluence pages, and act on service requests.
Spojit connects to this server through a custom MCP server connection, so you add it with Add custom server rather than from the connector catalog. Atlassian maintains it and decides which tools it offers; see Atlassian’s Rovo MCP Server documentation for the current list.

​
Before you start

  • An Atlassian Cloud site. The tools can only reach what your Atlassian account can already see.
  • For OAuth sign-in, an organization admin must allow Spojit’s domain. Atlassian blocks OAuth clients from domains that are not on the list.
1

Allow Spojit's domain (organization admin)

In Atlassian Administration, select your organization, then Rovo > Rovo MCP server. Select Add domain and add the domain you use Spojit on (for example miraxa.spojit.com), following Atlassian’s domain pattern guidance.

​
Server URL

​
Connect in Spojit

1

Add a custom server

Go to Connections and click Add custom server. Enter a Name such as Atlassian and paste the Server URL.
2

Keep Auto authentication

Leave Authentication on Auto, choose a visibility, and click Save & connect.
3

Approve access in Atlassian

Atlassian opens its consent page. Sign in, choose the site, and approve. Spojit marks the connection Connected and refreshes the token automatically.

​
Alternative: an API token

For unattended workflows that should not depend on one person’s sign-in, Atlassian supports API tokens. An organization admin must first turn on API token under Rovo > Rovo MCP server > Authentication. Domain allowlisting does not apply to token connections.
1

Create a token

Create an API token at id.atlassian.com/manage-profile/security/api-tokens.
2

Encode your email and token

Atlassian expects Basic authentication: your account email and the token joined by a colon, then base64 encoded.
3

Add the server with Token authentication

In Add custom server, choose Token. Paste the encoded value as the Token, keep Header name as Authorization, set Prefix to Basic, and click Add.
Atlassian notes that a personal API token sent as a Bearer token falls back to read-only tools. Use the Basic format above for write access. Service account API keys use Bearer instead.

​
Use it in a workflow

Add a Connector node, pick your Atlassian server under Custom Servers, and choose Agent Mode or Direct Mode. See Use a custom server in a workflow.

​
Troubleshooting

The Spojit domain is not on your organization’s allowed list. Ask an organization admin to add it under Rovo > Rovo MCP server, then click Reconnect on the connection.
Use Basic authentication with your email and token as shown above, not a Bearer token.
API token authentication is off for the organization. An organization admin can turn it on under Rovo > Rovo MCP server > Authentication.

​
Learn more