ClawHub

Maverick Confluence Mcp

Work with Confluence workspace content through Atlassian Rovo's hosted MCP server. Thin pass-through to Atlassian's official MCP; the live tool catalog is whatever that server advertises. Use when the user asks about Confluence pages, spaces, docs, comments, or knowledge-base updates.

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisReview

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install maverick-confluence-mcp

Confluence

How to use this skill

This skill is a thin pass-through to Atlassian Rovo's hosted MCP server at https://mcp.atlassian.com/v1/mcp/authv2. The live server is the source of truth for what tools exist, what they're called, what arguments they take, and any per-server instructions the server publishes.

Always invoke through bash {baseDir}/scripts/invoke.sh — never call mcporter directly. The wrapper seeds the OAuth vault from the env-supplied tokens when needed, then calls mcporter.

Step 1 — Discover the live tool catalog and any server-published usage instructions. Always run this first; do not rely on tool names from memory:

bash {baseDir}/scripts/invoke.sh list maverick-confluence-mcp --schema

The output includes the server's Instructions: field (read it) and a JSON Schema for every tool's parameters. Treat this as the authoritative reference for the rest of the session.

Step 2 — Call any tool from the catalog using the form maverick-confluence-mcp.<tool>:

bash {baseDir}/scripts/invoke.sh call maverick-confluence-mcp.<tool> <arg>=<value> ...

Add --output json for structured output (also surfaces transport errors as JSON envelopes):

bash {baseDir}/scripts/invoke.sh call --output json maverick-confluence-mcp.<tool> ...

Safety

Atlassian Rovo MCP can perform actions with the connected user's Confluence permissions. Read and search tools are safe to call while gathering context. Tools that create, update, publish, comment on, or otherwise mutate Confluence content should only be invoked after clear user intent.

Authentication

Credentials are available to the agent runtime through required env vars. The wrapper seeds mcporter's vault as needed before each call. mcporter handles authentication automatically: it reads tokens from the vault, sends them with each request, and refreshes them on expiry. Just call tools.

The only failure mcporter can't recover from on its own is grant revocation (the user revoking access in the upstream service's UI). It manifests as calls persistently failing with auth errors that don't clear on retry — at that point surface it to the user and ask them to re-authorize the integration.

Troubleshooting

Atlassian organization admins can restrict MCP authentication methods and product access. If the schema is empty or calls fail despite valid credentials, ask the user to confirm Atlassian Rovo MCP access and granted Confluence scopes with their site admin.

References