Build your own GitHub MCP server
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 15 nodes and runs when an MCP client calls one of its tools (plus 1 other trigger). Along the way it connects GitHub.
How it runs
Trigger: When an MCP client calls one of its tools (plus 1 other trigger).
- Operation (Switch): routes items into 3 branches
- Get Many Issues (GitHub): work with repository
- Get Single Issue (GitHub): get
- Create Comment (GitHub): create comment
- Simplify Issues (Edit Fields (Set)): sets 8 fields: issue_number, title, url…
- Get Comments (HTTP Request): calls an HTTP API
- Get Response (Edit Fields (Set)): sets 1 field: response
- Aggregate: combines items into one
- Simplify Comments (Edit Fields (Set)): sets 7 fields: id, issue_url, user…
- Aggregate: combines items into one
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Switch
n8n-nodes-base.switch - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Call n8n Workflow Tool
@n8n/n8n-nodes-langchain.toolWorkflow - Edit Fields (Set)
n8n-nodes-base.set - Aggregate
n8n-nodes-base.aggregate - HTTP Request
n8n-nodes-base.httpRequest - GitHub
n8n-nodes-base.github
From the author
This n8n demonstrates how to build your own Github MCP server to personalise it to your organisation's repositories, issues and pull requests. This n8n implementation, though not as fully featured as the official MCP server offered by Github, allows you to…