confluence-connect

name	confluence-connect
description	Set up and verify Confluence integration. Use when the user says 'connect to Confluence', 'set up Confluence', or 'configure Confluence'.

Confluence — Connect and Verify

Goal

Validate Confluence connectivity and store working credentials so push-doc and sync operations work without re-prompting.

Supports two connection modes:

• REST API — direct HTTP calls using email + API token
• MCP Server — uses the Atlassian MCP server (same server as JIRA if already configured)

---

Security Check First

Confirm _superml/config.yml is in .gitignore before proceeding (same check as jira-connect).

---

Step 1: Choose Connection Mode

Check _superml/config.yml for jira.connection_mode. If JIRA is already configured in MCP mode, suggest using the same MCP server:

"JIRA is configured to use MCP Server. Would you like Confluence to use the same MCP server? (recommended — same Atlassian credentials)

1. Yes, use the same MCP server
2. No, use REST API for Confluence"

If JIRA is not configured, ask:

"How would you like to connect to Confluence?

1. REST API — email + API token, direct HTTP calls
2. MCP Server — Atlassian Remote MCP Server or a self-hosted MCP package"

---

Path A: REST API Connection

A1: Collect Confluence Details

Ask:

1. Confluence base URL: e.g., https://yourorg.atlassian.net/wiki
2. Space key: e.g., or — the key of the space to publish docs to