Use BankSync with Atlassian Rovo

Atlassian provides a remote MCP server (mcp.atlassian.com) that gives AI tools access to Jira, Confluence, and Compass. By configuring both the Atlassian MCP server and BankSync in the same AI client, you can build workflows that combine your project management data with live bank data — for example, linking budget updates in Jira to your actual bank transactions.

Prerequisites

A BankSync account with at least one connected bank
An API key with all permission scopes (created from Workspace menu → Developers)

Authentication: The Atlassian MCP server uses OAuth 2.1 — your browser will open for authorization on first use. No API key is required for the Atlassian side.

Configure Both Servers in Cursor

Add both Atlassian and BankSync to .cursor/mcp.json:

.cursor/mcp.json — Atlassian + BankSync

{
  "mcpServers": {
    "atlassian": {
      "url": "https://mcp.atlassian.com/v1/mcp"
    },
    "banksync": {
      "url": "https://mcp.banksync.io",
      "headers": {
        "X-API-Key": "bsk_your_api_key_here"
      }
    }
  }
}

Configure in Claude Desktop

claude_desktop_config.json — Atlassian + BankSync

{
  "mcpServers": {
    "atlassian": {
      "type": "http",
      "url": "https://mcp.atlassian.com/v1/mcp"
    },
    "banksync": {
      "type": "http",
      "url": "https://mcp.banksync.io",
      "headers": {
        "X-API-Key": "bsk_your_api_key_here"
      }
    }
  }
}

Deprecation note: The legacy Atlassian SSE endpoint (/v1/sse) will stop working after June 30, 2026. Always use /v1/mcp (Streamable HTTP).

Verify Your Connection

After configuring your client, restart it and try these prompts to verify the connection is working:

“List my workspaces”

“What banks do I have connected?”

“What’s my checking account balance?”

Troubleshooting

“No tools available” or MCP server not listed

Make sure you restarted your AI client after editing the configuration file.
Verify the JSON is valid (no trailing commas, correct brackets).
Check that the URL is exactly https://mcp.banksync.io.

“Authentication failed” or “Invalid API key”

Confirm the key starts with bsk_ and has not been revoked.
Ensure the key is in the headers object under X-API-Key.
Check for accidental whitespace or newlines around the key value.

Tools are listed but return errors

Verify your API key has the required scopes. For full access, select all scopes when creating the key.
Make sure you have at least one bank connected in the BankSync app.
Check that you are passing the correct workspace ID when prompted.

Connection timeout or network errors

The MCP server uses Streamable HTTP transport. Ensure your network or proxy allows outbound HTTPS connections.
If using a VPN or firewall, allow connections to mcp.banksync.io.
Try the connection from a different network to rule out local issues.
If your client does not support remote HTTP servers, use the npm package instead: npx -y @banksync/mcp

Debugging with MCP Inspector

Use the MCP Inspector to test the connection independently of your AI client.
Run: npx @modelcontextprotocol/inspector --url https://mcp.banksync.io --header "X-API-Key: bsk_your_key"
If the Inspector connects successfully but your client does not, the issue is with your client configuration.