Skip to content

in_reply_to_id is un #885

@juvis-bmkim

Description

@juvis-bmkim

Describe the bug
The GitHub MCP server does not support the in_reply_to_id parameter when creating issue comments, which prevents users from creating threaded replies to specific comments. This functionality is available in the GitHub REST API but is missing from the MCP server implementation.
Affected version
Please run docker run -i --rm ghcr.io/github/github-mcp-server ./github-mcp-server --version and paste the output below
[Please run the command above and paste the output here]
Steps to reproduce the behavior

Try to create an issue comment that replies to a specific existing comment
Look for in_reply_to_id parameter in the available MCP tools (e.g., issues.create_comment or similar)
The parameter is not available in the tool schema
Attempt to create a threaded reply fails - comments are created as top-level comments instead of replies

Expected vs actual behavior
Expected behavior:

The MCP server should support the in_reply_to_id parameter for issue comment creation
Users should be able to create threaded replies to specific comments, similar to the GitHub REST API endpoint POST /repos/{owner}/{repo}/issues/{issue_number}/comments with in_reply_to_id parameter
The created comment should appear as a reply to the specified parent comment in the GitHub UI

Actual behavior:

The in_reply_to_id parameter is not available in the MCP server's issue comment tools
All comments are created as top-level comments regardless of the intention to reply to a specific comment
No way to create threaded comment conversations through the MCP server

Logs
No specific error logs since the parameter simply doesn't exist in the tool schema. The issue is a missing feature rather than a runtime error.
Additional Context:
This feature would be particularly useful for:

AI agents that need to participate in existing comment threads
Maintaining context in code review discussions
Creating more organized and readable issue conversations
Matching the full functionality of the GitHub REST API

Reference:
GitHub REST API documentation: https://docs.github.com/en/rest/issues/comments#create-an-issue-comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions