How to add an MCP server to GitHub Copilot

Checked against GitHub Copilot's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

1. 1. Choose a server and see what it needs

   GitHub Copilot can keep a server in a user file, in a project file or in the repository's cloud-agent settings. The add steps after this one are for the Copilot CLI.

   • Playwright MCP: runs locally, no key needed.
   • Figma MCP Server: hosted, connect by URL, no key needed.
   • Firecrawl MCP Server: runs locally, can take FIRECRAWL_API_KEY.
   • Where GitHub Copilot can keep a server: user (~/.copilot/mcp-config.json), project (.mcp.json or .github/mcp.json) and the repository's cloud-agent settings.

2. 2. Add a local server (Playwright MCP)

   Playwright MCP runs locally. It is added with copilot mcp add, and the file entry records it with the type local and a tools list.

   copilot mcp add playwright-mcp -- npx -y @playwright/mcp@0.0.82

   Copy

   {
     "mcpServers": {
       "playwright-mcp": {
         "type": "local",
         "command": "npx",
         "args": [
           "-y",
           "@playwright/mcp@0.0.82"
         ],
         "tools": [
           "*"
         ]
       }
     }
   }

   Copy

   • This is for the Copilot CLI. The Copilot cloud agent takes its MCP servers from the repository's Copilot settings instead.

3. 3. Add a remote server (Figma MCP Server)

   Figma MCP Server is hosted. The command uses --transport http with the URL, and the file entry has the type http and the same URL.

   copilot mcp add --transport http figma https://mcp.figma.com/mcp

   Copy

   {
     "mcpServers": {
       "figma": {
         "type": "http",
         "url": "https://mcp.figma.com/mcp",
         "tools": [
           "*"
         ]
       }
     }
   }

   Copy

   • This is for the Copilot CLI. The Copilot cloud agent takes its MCP servers from the repository's Copilot settings instead.

4. 4. Keep API keys out of the file (Firecrawl MCP Server)

   Firecrawl MCP Server can take FIRECRAWL_API_KEY. The notes say the Copilot CLI page describes no variable interpolation, so the example command and file hold the placeholder YOUR_FIRECRAWL_API_KEY, and the command passes it with --env.

   copilot mcp add firecrawl-mcp-server --env FIRECRAWL_API_KEY=YOUR_FIRECRAWL_API_KEY -- npx -y firecrawl-mcp@3.34.1

   Copy

   {
     "mcpServers": {
       "firecrawl-mcp-server": {
         "type": "local",
         "command": "npx",
         "args": [
           "-y",
           "firecrawl-mcp@3.34.1"
         ],
         "env": {
           "FIRECRAWL_API_KEY": "YOUR_FIRECRAWL_API_KEY"
         },
         "tools": [
           "*"
         ]
       }
     }
   }

   Copy

   • The Copilot CLI page describes no variable interpolation, so env and header values are literal. For the cloud agent, store secrets with names that start with COPILOT_MCP_ and reference them in the config.
   • This puts the value in mcp-config.json in plain text; keep that file out of version control.
   • This is for the Copilot CLI. The Copilot cloud agent takes its MCP servers from the repository's Copilot settings instead.
   • FIRECRAWL_API_KEY (optional): Your API key for Firecrawl.

5. 5. Restart or reload if the server does not appear

   Use this step if the server does not appear. It covers a server added with /mcp add, hand-editing the config file, and folder trust.

   • A server added with /mcp add is available immediately without restarting the CLI. The docs do not say whether hand-editing mcp-config.json needs a reload.
   • Project servers load only after you trust the folder. The cloud agent runs MCP tools without asking, so list only the tools it needs.

copilot mcp list