Proposal: Integrating Claude Code with GitHub Copilot Agent Mode via MCP

[Hugues862]

Select Topic Area

Question

Copilot Feature Area

Copilot Agent Mode

Body

I primarily use Claude Code, but I’ve been considering the possibility of integrating it with an MCP server alongside GitHub Copilot’s Agent Mode. Here’s the idea:

When you create an issue in your GitHub repository and assign GitHub Copilot, it can:

• Spin up a new branch
• Implement the proposed changes
• Open a pull request (PR)

This flow is very intuitive and well-integrated into VSCode, especially with the GitHub Copilot extension and GitHub PR extension.

Would it be possible to plug Claude Code’s MCP into this flow?

• Copilot would act as the orchestrator, managing issues, branches, and PRs
• Claude Code would handle the actual code generation and implementation

This setup could allow for fully remote, issue-driven development, from ideation to merge, entirely from your phone.

Has anyone already managed to:

• Connect Claude Code’s MCP to GitHub Copilot Agent Mode?
• Orchestrate development through this hybrid setup?

To be clear, I am not talking about using it in chat directly, that works fine, i'm really talking about the spawned agent when assigning a issue.

I’d really appreciate any insights, and if anyone’s interested, let’s explore this together.

[ArchiveTanvir]

Whoa, this is a super cool idea. Haven’t seen anyone do this kind of Copilot + Claude hybrid yet, but it totally makes sense. Copilot could manage the GitHub stuff and Claude could handle the actual code.

I think the tricky part would be getting Copilot Agent Mode to trigger external tools like Claude, since it’s pretty closed right now. But maybe with GitHub webhooks or custom Actions, you could route issue events to Claude’s MCP and make it work that way.

[kokatesaurabh]

Hey Hugues862,

Your idea to combine Claude Code’s MCP with GitHub Copilot’s Agent Mode for issue-driven development is brilliant—it’s like having the best of both worlds: Copilot’s tight GitHub integration and Claude’s powerful code generation! 😎 While I haven’t seen this exact hybrid setup in the wild, it’s definitely feasible with some configuration, and I’d love to help you brainstorm how to make it work.

Here’s a concise approach to explore this:

Leverage the GitHub MCP Server: Set up the remote GitHub MCP server (available via GitHub’s recent release) in VS Code to let Copilot Agent Mode handle GitHub tasks like creating branches and PRs. Configure it in your .vscode/mcp.json file with OAuth for secure access to your repo (see GitHub Docs for setup: https://docs.github.com/en/copilot). This keeps Copilot as the orchestrator for issue management.
Integrate Claude Code via MCP: Claude Code supports MCP servers for tool integration (as noted in Anthropic’s Claude 4 announcement). You can configure a custom MCP server for Claude Code to handle code generation. Use the Claude Code SDK to define tools for writing and editing code, and host it locally or remotely. In VS Code, add this server to your .vscode/mcp.json alongside the GitHub MCP server, ensuring Claude is accessible to Copilot’s Agent Mode.
Orchestrate with Webhooks or Actions: As CoderShuvo suggested, Copilot Agent Mode’s native flow (issue → branch → PR) is somewhat closed, so you’ll need a bridge. Set up a GitHub Action or webhook to trigger when Copilot picks up an issue. This can send the issue details to your Claude Code MCP server, which generates the code and pushes it back to the repo via the GitHub MCP server. For example, a webhook could POST issue data to a Claude Code endpoint, which responds with generated code that Copilot commits.
Test the Workflow: Start with a simple issue in your repo (e.g., “Add a login function”). Assign it to Copilot, which creates a branch. Use a custom GitHub Action to call Claude Code’s MCP server with the issue description, let Claude generate the code, and have Copilot commit it to the branch and open a PR. Test this in a small project to iron out kinks, like ensuring Claude’s code aligns with your repo’s standards.
Challenges to Watch:

Tool Coordination: Copilot Agent Mode might not natively call Claude’s MCP tools, so the webhook/Action bridge is critical. Test with a simple Action first (e.g., a Node.js script to call Claude’s API).
Authentication: Ensure both MCP servers (GitHub and Claude) use secure auth (OAuth for GitHub, API keys for Claude). Avoid hardcoding credentials in mcp.json.
Latency: Remote workflows, especially from a phone, might introduce delays. Optimize by keeping Claude’s MCP server lightweight.
Next Steps: Check out the Claude Code SDK for setting up its MCP server, and explore GitHub’s webhook docs for routing issue events. If you’re up for it, share your repo’s setup or any specific blockers, and we can dig deeper together! Anyone else tried a hybrid like this? Let’s make this remote dev dream a reality! 🚀

[Hugues862]

Thank you very much for the input. I will look into this a bit more when I have some free time to spare. If I have any new information or make any advancements, I will post them here.

[Kidhurshan]

Your hybrid approach of combining Claude Code's MCP capabilities with GitHub Copilot's Agent Mode is absolutely fascinating and technically sound! While this exact integration isn't commonly documented yet, it's definitely achievable with the right architectural approach.

The key is creating a bridge between Copilot's native issue-to-PR workflow and Claude Code's powerful generation capabilities. You'd essentially set up dual MCP servers in your VS Code environment - GitHub's official MCP server for repository management and a custom Claude Code MCP server for code generation. The missing piece is orchestration, which you can solve with GitHub Actions or webhooks that trigger when Copilot picks up an issue, routing the requirements to Claude Code and feeding the generated code back into Copilot's workflow.

The technical challenges are manageable: authentication coordination between both MCP servers, potential latency in remote workflows, and ensuring the tools communicate properly through your webhook bridge. But the payoff - fully remote, issue-driven development from your phone - makes this incredibly compelling.

I'd recommend starting with a simple test setup using GitHub's webhook documentation and the Claude Code SDK to build your MCP bridge. If you'd like to explore this further or need help with specific implementation details, I'm happy to dive deeper into the technical architecture. This kind of hybrid workflow could really change how we think about remote development!

[truoineo]

Forgive me if I've misunderstood, but what exactly is the benefit of combining the two? If your desired functions are about Github management, can you just connect Claude Code to Github MCP? I don't see the point of using Copilot in this workflow.

[medley56]

I agree. That's exactly what I'm trying to do and that's how I ended up reading this thread.

[tannerbroberts]

It seems like either platform will work well for this, given the recent development of Claude Code's "Agent skills", which are basically just a folder of hardened instructions that make agents more likely to succeed in a given environment. I've only seen this implemented in Claude Code, but it seems like it'll bleed into other providers.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐