Copilot is really behind major players in terms of built-in MCP servers / connectors #205330
Unanswered
andriy-ah
asked this question in
Copilot Conversations
Replies: 1 comment
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Copilot Agentic Workflows
Body
What the title says. Our company is using both Copilot and Claude Code. I want us to use Copilot more and want everyone else to do the same as it allows to use models from different vendors. But the difference in level of integrations comparing with Claude Code is massive and it becomes really a hard sell.
In Claude you can connect a bunch of services in a couple of clicks, many things are built-in. In Copilot, even though you have a list of some MCP servers, you need to fill in some fields and I didn't find any good instructions on that, built-in MCP list is empty.
Makes it really hard to go with Copilot. Don't you see you are losing here to the competition?
All reactions