Why does confluence_reply_to_comment create a footer comment instead of an inline reply?
In mcp-atlassian 0.23.1 (PyPI install) on Windows against Confluence Server/Data Center, calling
confluence_reply_to_commentwith an inline comment id reports success but creates a comment with location "footer" instead of anchoring the reply to the inline thread. Is this a known bug, and is there a fix or workaround?Originally asked on GitHub: https://github.com/sooperset/mcp-atlassian/issues/1681
3 answers
Still open as of the last thread activity (Oct 2026); no patch or workaround was posted. The bug is confirmed by multiple users.
Why it happens: on Confluence, footer comments are created against the page container, while inline replies go to the inline comment's own children collection via a different endpoint.
confluence_reply_to_commenthands the inline id to the footer-comment path, and that request has no field that can carry the inline anchor, so the reply is created with locationfootereven though the tool reports success.A closer look in the thread shows the reply isn't fully detached: it does thread under the inline comment (deleting it from the thread removes it), but it is created with the wrong location type, so it bumps the page-bottom comment counter and never appears in the bottom feed — unlike
confluence_add_inline_comment, which doesn't touch that counter.Expected fix direction: the tool should resolve the comment id, detect that it is an inline comment, and use the inline reply call path — or, until that exists, error instead of silently falling back to footer placement. As general advice, you can verify the returned comment's
locationfield after the call and treat anyfooterresult on an inline reply as a failure.Reproduction from the report:
confluence_get_inline_comments(page_id: "433816914")gives inline comment id 474693379, thenconfluence_reply_to_comment(comment_id: "474693379", body: "Test reply"), thenconfluence_get_comments(page_id: "433816914")shows the new comment with locationfooter.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter passed an inline comment id (474693379) to
confluence_reply_to_commentwith a body, then re-fetched withconfluence_get_comments(page_id: "433816914"). The tool returned success but created the reply with location "footer", detached from the inline thread.Source: https://github.com/sooperset/mcp-atlassian/issues/1681 (opens external site)
Did this work for you?What @AndrianovaNataliya tried on GitHub (Partly worked)
A commenter tested the misplaced reply's lifecycle: it bumps the page-bottom comment counter while the bottom feed stays empty, and deleting the reply from the inline thread clears the counter and removes the reply. This shows the reply is linked to the inline parent but created with the footer location type.
Source: https://github.com/sooperset/mcp-atlassian/issues/1681#issuecomment-6142784318 (opens external site)
Did this work for you?
Related questions
- mcp-atlassian: 'JiraConfig' object has no attribute 'read_only' when calling create_issue
- mcp-atlassian Docker fails on startup with 'ValueError: I/O operation on closed file' — fixed?
- OAuth 2.0 for Confluence Data Center (on-prem) in mcp-atlassian?
- mcp-atlassian crashes with Pydantic 2.12.0: 'cannot specify both default and default_factory'
- mcp-atlassian Jira search_issues: 'requested API has been removed' error and total -1