Stay on top of GitHub issues without leaving your workspace. This setup lets team members browse recent issues and post replies through a connected MCP client, so you can review and respond faster. It is a good fit for support and engineering teams that live in GitHub and want a simple command style workflow.

Two triggers power the system. An MCP server trigger exposes three tools to your client Get Latest Issues, Get Issue Comments, and Add Issue Comment. A second trigger accepts calls from other n8n workflows. A Switch node routes each request to the right GitHub action. The flow pulls issues or a single issue, fetches its comments with a direct API call, and can post a new comment. Set and Aggregate nodes clean and bundle the final response so the client gets only the details that matter.

You need a GitHub account with access to the target repo and an MCP client that can call the server. Expect faster triage, fewer context switches, and clearer updates for your team. Typical use includes daily issue review, quick status checks, and posting standard replies. Turn on authentication on the MCP trigger before sharing access, and set default repo values to match your environment.

• MCP server trigger exposes three tools to your client for getting issues, reading comments, and posting replies.
• Switch node maps each operation to the correct path so requests are handled cleanly.
• GitHub nodes fetch many issues, get a single issue, and create a comment with your credentials.
• HTTP Request pulls the comments list from the issue comments URL for a complete thread view.
• Set nodes simplify fields so the client receives clean titles, numbers, links, and comment text.
• Aggregate nodes combine results into one response object for easy reading.
• Execute by another workflow trigger lets other n8n flows reuse these tools programmatically.

• Reduce manual issue review from 60 minutes to 10 minutes per day by listing only the latest items you need to see.
• Eliminate copy and paste between tools by replying to issues from one place.
• Improve response consistency by using a single path to fetch issues and comments.
• Support more requests with the same team by routing actions through clear tools.
• Connect your MCP client and GitHub so data stays in sync without extra steps.

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with GitHub. See the Tools Required section above for links to create accounts with this service.
3. In n8n, open any GitHub node and create credentials: Double click the node, on the Credential to connect with dropdown click Create new credential, then follow the on screen steps to integrate GitHub. Use a personal access token with repo scope or complete OAuth if offered.
4. In the MCP server trigger node, enable authentication and set allowed origins to match your client. Save the server URL for your client configuration.
5. Open the Switch node named Operation and confirm the operation names match your client calls getLatestIssues, getIssueComments, and addIssueComment.
6. Set the default repository in the tool nodes if needed. Look for the repo field in the tool workflow inputs and change it to your target owner and repo.
7. Test Get Latest Issues: Execute the workflow and call the MCP tool for latest issues. You should see simplified issue numbers, titles, and links in the response.
8. Test Get Issue Comments: Provide a valid issue number from your repo. Verify the flow fetches the single issue and then retrieves the full comments list.
9. Test Add Issue Comment: Use a known issue number and a short test message. Confirm the new comment appears in the GitHub thread and the response returns the link.
10. If you get permission errors, check your GitHub token scopes and make sure your account has access to the repository. If the MCP client cannot connect, recheck the trigger authentication settings and the server URL.