Atlassian Confluence
Let your coding agent create, update, search, and attach files on Confluence so product specs and runbooks stay in sync with what you ship.
Overview
com.mcparmory/atlassian-confluence is an MCP server for the Build phase that automates creating, searching, and managing Confluence pages and attachments from your AI coding agent.
What is this MCP server?
- Create and update Confluence pages from agent prompts without opening the browser
- Search workspace content and manage attachments with full automation support
- stdio MCP transport with uvx (PyPI) or Docker OCI install paths
- Published as com.mcparmory/atlassian-confluence v1.0.8 on the MCP Armory registry
- Pairs with Jira MCP when specs live in Confluence and work tracks in issues
- Server version 1.0.8 with 2 distribution packages (PyPI uvx and Docker OCI)
- stdio transport only per MCP Armory server schema
- Registry identifier mcparmory-atlassian-confluence on PyPI
Community signal: 25 GitHub stars.
What problem does it solve?
Switching between your editor and Confluence to update specs and runbooks breaks flow and leaves wiki content stale compared to the repo.
Who is it for?
Indie builders or tiny teams on Atlassian Cloud who want agent-driven wiki updates during feature work.
Skip if: Builders without Confluence, or those who only need local Markdown in the repo with no Atlassian stack.
What do I get? / Deliverables
After you register the server, your agent can read and write Confluence content in-thread so documentation updates ship with the same session as your code changes.
- Agent-callable tools to create, update, and search Confluence pages
- Attachment management against your Confluence spaces
- Live wiki content reflected in agent threads without manual copy-paste
Recommended MCP Servers
Journey fit
Confluence is where build-phase knowledge lives—architecture notes, API docs, and handoff pages—so the canonical shelf is Build before launch content marketing. Docs subphase covers wikis and internal documentation automation, which matches page CRUD, search, and attachment management on Confluence.
How it compares
MCP integration to Confluence Cloud—not a doc-writing skill or static site generator.
Common Questions / FAQ
Who is com.mcparmory/atlassian-confluence for?
Solo and small-team developers using Atlassian Confluence who want their coding agent to manage pages and attachments programmatically.
When should I use com.mcparmory/atlassian-confluence?
Use it during build and ship when you maintain internal specs, ADRs, or runbooks in Confluence and want updates without leaving the agent.
How do I add com.mcparmory/atlassian-confluence to my agent?
Add an MCP server entry with stdio transport, run via uvx mcparmory-atlassian-confluence or the ghcr.io Docker image, and configure Atlassian API credentials in the environment your client expects.