Cline

First complete Set up Jira and Confluence.

Open the MCP settings

In Cline, select the MCP Servers icon, open Configure, and select Configure MCP Servers. Edit the JSON file that Cline opens. This selects the active configuration for your editor and profile.

Add atlassian under mcpServers. Keep other server entries. Replace YOUR_NAME and the executable path with your local values.

{
  "mcpServers": {
    "atlassian": {
      "command": "/Users/YOUR_NAME/.local/bin/uvx",
      "args": [
        "mcp-atlassian==0.23.0",
        "--transport", "stdio",
        "--env-file", "/Users/YOUR_NAME/.config/tritonai/atlassian.env"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

disabled: false enables the server. The empty autoApprove list keeps tool calls subject to approval. See Cline's MCP configuration.

Check the connection

Save the file and restart the server from Cline's MCP settings. Inspect its tool list, then run the Jira and Confluence checks.

If Cline runs in a WSL or remote editor session, use the executable and credential file in that environment.

Cline CLI

For the CLI, run cline mcp and use its MCP wizard to register the same executable and arguments. This avoids assuming that the CLI uses your IDE configuration file. See the Cline MCP wizard.