confluence-fetch 0.13.0

Agent-first CLI for fetching Confluence Cloud page context as Markdown or JSON.

confluence-fetch

confluence-fetch fetches Confluence Cloud pages and turns them into agent-friendly output for CLI tools like Codex CLI and Claude Code.

It is designed for:

• Fetching page context from a Confluence URL
• Returning clean Markdown by default
• Returning structured JSON when needed
• Keeping secrets out of config files

Why

This tool exists to bring Confluence context into local agent workflows.

The primary use case is:

1. Set a token in an environment variable
2. Set your Confluence account email in config
3. Run confluence-fetch fetch <confluence-url>
4. Feed the result into an agent

Install

Target public install path:

uvx confluence-fetch --help

For local development, the repo will also keep a PEP 723 script entry point for uv run.

Quick Start

Set your Confluence token:

$env:CONFLUENCE_TOKEN = "<your-token>"

Set your Confluence account email:

uvx confluence-fetch config set-email "[e-mail]"

Fetch a page as Markdown:

uvx confluence-fetch fetch "https://your-domain.atlassian.net/wiki/spaces/ENG/pages/123456789/Example+Page"

Fetch the same page as JSON:

uvx confluence-fetch fetch --format json "https://your-domain.atlassian.net/wiki/spaces/ENG/pages/123456789/Example+Page"

Write output to a file:

uvx confluence-fetch fetch -o page.md "https://your-domain.atlassian.net/wiki/spaces/ENG/pages/123456789/Example+Page"

Include comments:

uvx confluence-fetch fetch --comments "https://your-domain.atlassian.net/wiki/spaces/ENG/pages/123456789/Example+Page"

Config

Optional user config lives at:

~/.confluence-fetch/config.toml

The config stores only environment variable names, never secret token values.

Example:

[defaults]
token_env_var = "CONFLUENCE_TOKEN"
email = "[e-mail]"

[domains."sona-systems.atlassian.net"]
token_env_var = "SONA_CONFLUENCE_TOKEN"

[domains."example.atlassian.net"]
token_env_var = "EXAMPLE_CONFLUENCE_TOKEN"

Resolution order:

1. --token-env ENV_VAR
2. domain-specific config match from the requested Confluence URL
3. [defaults].token_env_var
4. built-in default CONFLUENCE_TOKEN

Email resolution order:

1. [defaults].email
2. CONFLUENCE_EMAIL
3. compatibility fallback confluence_email

Config commands:

confluence-fetch config show
confluence-fetch config set-default-token-env ENV_VAR
confluence-fetch config set-email EMAIL
confluence-fetch config clear-email
confluence-fetch config set-domain-token-env DOMAIN ENV_VAR
confluence-fetch config remove-domain DOMAIN

Example:

uvx confluence-fetch config set-domain-token-env sona-systems.atlassian.net SONA_CONFLUENCE_TOKEN

config show displays the effective token env var names, whether they are set or missing, and the configured default email. It never prints token values.

Output

confluence-fetch supports:

• --format markdown
• --format json

Markdown is the default.

Diagnostics go to stderr. Payload output goes to stdout unless --output is used.

Development

Implementation target:

• Python >=3.11
• installable PyPI package
• PEP 723 wrapper for uv run

Auth

confluence-fetch uses Basic auth with a Confluence account email plus API token.

Secrets are not written to config.

Scoped API Token Permissions

For scoped Confluence API tokens, grant only the scopes needed for the features you use:

Feature	Required scope
Fetch page Markdown or JSON	read:page:confluence
Include comments with --comments	read:comment:confluence
Download image assets with --download-images	read:attachment:confluence
Resolve comment author display names	read:user:confluence

Recommended full token for all current features:

read:page:confluence
read:comment:confluence
read:attachment:confluence
read:user:confluence

If read:user:confluence is missing, comments still render, but author names fall back to stable account IDs when Confluence does not include display names in the comment payload.

License

MIT. See LICENSE.

Status

This repo is currently being built around an agent-first v2 spec.