Skip to main content

runspec-confluence

A Confluence runnable for runspec, ported from the Atlassian MCP server onto atlassian-python-api — pages, spaces, comments, labels, restrictions and attachments, on Cloud and Server/Data Center. One runnable — confluence — with 20-plus verbs. pip install it into a venv and it's discoverable by runspec local, runspec serve (MCP), and runspec-console.

runspec serve flattens each verb into a leaf MCP tool (confluence_get-page, …). Read verbs are autonomy = "autonomous"; writes are autonomy = "confirm".

Install

pip install runspec-confluence

Verbs

Area Verbs
Search search (CQL), search-text, search-by-label
Spaces list-spaces, get-space, get-space-pages
Pages (read) get-page, get-page-children, get-page-ancestors, get-page-history, get-page-restrictions, whoami
Pages (write) create-page, update-page, delete-page, move-page
Labels & comments get-labels, add-label, get-comments, add-comment
Attachments get-attachments, download-attachments, upload-attachment, delete-attachment

Page bodies pass in a Confluence representation via --content-format (storage / wiki / editor / markdown); markdown is converted to storage XHTML client-side (best-effort).

Auth — env vars only

export CONFLUENCE_URL=https://your-org.atlassian.net/wiki
# Cloud (API token):
export CONFLUENCE_USERNAME=you@example.com
export CONFLUENCE_API_TOKEN=<api-token>
# …or Server/DC (Personal Access Token):
export CONFLUENCE_PERSONAL_TOKEN=<pat>

Cloud vs Server/DC is detected from a .atlassian.net host or set with CONFLUENCE_CLOUD. Every verb takes --env, selecting CONFLUENCE_<ENV>_* prefixed vars. The PAT can instead ride the runspec-console secret channel via the optional --confluence-pat (a password-typed arg, refused on the CLI, kept out of logs).

confluence search --cql "space = OPS AND type = page"
confluence get-page --page-id 123456
confluence create-page --space OPS --title "Runbook" --content-format markdown --body "# Steps"

Public Python API

The pure logic is in runspec-confluence-core — over atlassian-python-api + markdown, no runspec dependency, no entry points. Every op takes a ConfluenceConfig first arg and raises ConfluenceError, so a private wrapper can inject credentials and bake in a default space / env:

from runspec_confluence_core import config_from_env, build_client, get_page

cfg = config_from_env(env="prod")
page = get_page(cfg, page_id="123456")

Development

python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
ruff check . && ruff format --check .
pytest

Metadata

Release files for runspec-confluence 0.6.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for runspec-confluence 0.6.1
File Size Uploaded
runspec_confluence-0.6.1.tar.gz 11.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for runspec-confluence 0.6.1
File Interpreter ABI Platform
runspec_confluence-0.6.1-py3-none-any.whl Python 3 none any Details

Total release size: 20.6 kB

Release files / runspec_confluence-0.6.1.tar.gz

Download URL runspec_confluence-0.6.1.tar.gz
Size 11.7 kB
Tags Source
SHA-256 checksum
How to use checksums
8d75a3031c01b011b8a7b2a4c4e310a7d45c8fc06fbc368e1c96817c4c53c32f
BLAKE2b-256 checksum
How to use checksums
ca07d467b0cbce9c584ccb04eb23292eb814653b97f5764a784a148b00af1a20
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

Release files / runspec_confluence-0.6.1-py3-none-any.whl

Download URL runspec_confluence-0.6.1-py3-none-any.whl
Size 8.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f367cd2c07792821734093498f3f81bd657dd59dc0c27562aab14c1021d9d6d8
BLAKE2b-256 checksum
How to use checksums
975378b8613412174425cfa1c4222b7cb37eda530815ea064e84c5ac0d488f51
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.0

2 release files

0.7.0

2 release files

This release

0.6.1 This release

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page