managePages and manageComments each take an action and validate only the parameters that action needs, so create, update, delete and read share one definition. The Markdown conversion matters more than it sounds: Confluence storage format is not Markdown, and writing it by hand is where most integrations produce broken pages.
A TypeScript server over the Confluence REST API. Eight tools: two combined managers that take an action parameter, plus space, page, comment and search reads.
- Eight tools, consolidated down from twelve
- Pages created, updated, deleted, and fetched as metadata or full content, through one action parameter — managePages
- A page fetched precisely by its title — getPageByPrettyUrl, and a space's information — getSpace
- Comments created, updated, deleted and replied to, both ordinary and inline, through one manager — manageComments
- A page's comments with paging, and one comment in detail — getPageComments, getComment
- Content searched with CQL, falling back to a basic search when the CQL is malformed — searchContent, and comments searched within a space — searchComments
- Markdown detected and converted to HTML automatically on page and comment writes, plus Markdown export of page content
- HTTP keep-alive, response compression, a configurable request timeout and automatic retry on failure
CONFLUENCE_URL, plus either CONFLUENCE_ACCESS_TOKEN, which the project recommends, or CONFLUENCE_USERNAME with CONFLUENCE_PASSWORD. Node with npm; the package publishes as @howbuy/mcp-server-confluence-ts and runs from dist/index.js. PORT, NODE_ENV, TIMEOUT and REJECT_UNAUTHORIZED are optional.
One command plus a key — npx -y @smithery/cli@latest run @enjoyzl/mcp-server-confluence-ts --config '{"confluenceUrl":"your-confluence-url","confluenceUsername":"your-username","conflue, then supply credentials