Copilot CLI Tutorial #8 - MCP Servers

Why It Matters

Connecting MCP servers lets Copilot interact directly with external platforms (GitHub, Figma, databases), enabling automated workflows like fetching issues, making PRs, or translating designs into code — a meaningful boost to developer productivity and toolchain integration.

Summary

The video explains how to connect MCP (Model Context Protocol) servers to the Copilot CLI so Copilot — acting as an MCP client — can access external services and expose additional tools to AI models. The presenter demonstrates built-in MCP servers (a read-only GitHub server) to list repo issues, then walks through adding and authenticating a Figma MCP server via its HTTP URL and selecting which tools to expose. He shows how to copy a Figma design node link (via Dev Mode) and ask Copilot to inspect that node so the model can extract design details for implementation. The tutorial covers the CLI steps for adding a server, configuring tools, authenticating, and invoking server tools from Copilot.

Original Description

In this Copilot CLI tutorial, I'll show you how to adopt an AI-assisted development workflow using commands, skills, MCP servers, plan mode and custom agents.

🍿👇 Get early access to the whole course on NetNinja.dev

https://netninja.dev/p/copilot-cli-tutorial

🔥👇 Get access to ALL Masterclasses & premium courses with a Net Ninja Pro membership:

https://netninja.dev/p/net-ninja-pro/#prosignup

🔗👇 Get the Starter Project on GitHub:

https://github.com/iamshaunjp/WordSprint

🔗👇 Copilot CLI Docs:

https://docs.github.com/en/copilot/how-tos/copilot-cli

🔗👇 Model Comparison:

https://docs.github.com/en/copilot/reference/ai-models/model-comparison#recommended-models-by-task

🔗👇 Astro Crash Course:

https://www.youtube.com/watch?v=CF3drb6H3Yw&list=PL4cUxeGkcC9hXL99yOeCcUrdUee8u36s3