Extending Copilot with MCP tools
1. Extending Copilot with MCP tools
Welcome to the last video in the course, where we'll explore how to extend GitHub Copilot using MCP servers.2. What is the Model Context Protocol?
MCP,3. What is the Model Context Protocol?
or Model Context Protocol,4. What is the Model Context Protocol?
is an open-source standard that allows Copilot to use external tools and services through a unified interface.5. What is the Model Context Protocol?
Think of it6. What is the Model Context Protocol?
as a bridge between AI agents, like GitHub Copilot, and the outside world.7. How MCP servers work
MCP servers expose tools—such as file system operations, databases, or API calls—in a standardized way.8. How MCP servers work
Instead of needing a custom integration for each service, Copilot can simply connect to an MCP server and immediately gain access to its tools.9. How the MCP works with GitHub Copilot
So, how does MCP work with GitHub Copilot? The architecture is straightforward. The code editor, in this case VS Code, acts as an MCP client.10. How the MCP works with GitHub Copilot
It connects to MCP servers, which provide specific tools.11. How the MCP works with GitHub Copilot
So, when we ask Copilot something in agent mode, it can decide whether to call one of these tools.12. How the MCP works with GitHub Copilot
The request flows from Copilot, through the MCP client, to the server,13. How the MCP works with GitHub Copilot
and then back to us with a result—all inside the Chat view.14. Focus on usage, not protocol
For simplicity, we'll now focus on how to set up and use MCP with Copilot,15. Focus on usage, not protocol
leaving the technical details of the protocol itself out of the scope of this course.16. Built-in Copilot tools
By default, Copilot already comes with some built-in tools, like githubRepo, a tool to inspect repositories. However, these built-in tools are limited in scope.17. Why MCP servers matter
For example, what if you want to list issues, get commit details, or create pull requests?18. Why MCP servers matter
That's where MCP servers come in!19. MCP servers extend Copilot's toolset
By installing the GitHub MCP server, you unlock a bigger set of actions.20. MCP servers extend Copilot's toolset
In other words,21. MCP servers extend Copilot's toolset
MCP servers extend Copilot far beyond what's available out of the box.22. The GitHub MCP server in action
The easiest way to get started is through the MCP Registry. You simply open the registry, browse the available servers, and click "Install in VS Code" on the one you need. The process feels almost identical to installing a regular VS Code extension. Once installed, your MCP servers appear in the Extensions view under MCP Servers – Installed. Your MCP servers will also appear in the Chat tools list. Here, you can see that Copilot now has access to three categories of tools: built-in tools, extensions, and MCP servers. For example, after installing the GitHub MCP server, you'll see the expanded set of GitHub-related tools available. Now try asking: "List my latest commits to this repo." Copilot will call the GitHub MCP server tool, fetch your issues, and display them directly in chat. You can even reference tools explicitly in your prompt by typing # followed by the tool's name. For example, you could say "#create_pull_request from development to master branch", and Copilot will help you do that; no need to create it manually from the GitHub interface.23. MCP security considerations
One last but important note:24. MCP security considerations
MCP servers can perform actions that change files,25. MCP security considerations
databases,26. MCP security considerations
or other resources.27. MCP security considerations
Always be mindful of what a tool is about to do,28. MCP security considerations
and only install servers from trusted sources.29. Let's practice!
Now, it's time to practice with a few exercises!Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.