--- title: Using MCP Servers with GitHub Copilot CLI | daily.dev description: GitHub Copilot CLI has the GitHub MCP server built in, so no extra configuration is needed for GitHub context. Custom MCP servers extend the CLI with docs... canonical: https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Using MCP Servers with GitHub Copilot CLI | daily.dev og:description: GitHub Copilot CLI has the GitHub MCP server built in, so no extra configuration is needed for GitHub context. Custom MCP servers extend the CLI with docs... og:url: https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc og:image: https://api.daily.dev/og/posts/yht9GRxjC.png og:image:alt: Using MCP Servers with GitHub Copilot CLI og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Using MCP Servers with GitHub Copilot CLI **[We Are .NET](https://daily.dev/sources/wearedotnet)** · 12 min read · 0 upvotes · 0 comments ## Summary GitHub Copilot CLI has the GitHub MCP server built in, so no extra configuration is needed for GitHub context. Custom MCP servers extend the CLI with docs lookup, browser automation, and platform APIs. Three setup paths are covered: the interactive /mcp add wizard, the copilot mcp add terminal command, and direct editing of ~/.copilot/mcp-config.json. Transport options are STDIO (local processes), HTTP (remote services), and SSE (legacy/deprecated). Tool scoping is handled at two levels: the tools filter in server config and runtime --allow-tool/--deny-tool flags. The /mcp search command provides experimental registry discovery. Concrete examples include Playwright MCP for browser automation and Context7 MCP for current library documentation. Key pitfalls include duplicating the built-in GitHub server, confusing server installation with tool approval, using SSE as default, and careless secret storage. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I add a custom MCP server to GitHub Copilot CLI from the terminal? Use the copilot mcp add command, putting the server command after a double dash for local STDIO servers, for example: copilot mcp add playwright -- npx -y @playwright/mcp@latest. For remote servers, add --transport http along with the URL. Additional flags include --env for environment variables, --header for HTTP headers, --tools to filter exposed tools, and --timeout for timing control. _daily.dev surfaces practical CLI configuration guides for developers wiring MCP servers into their agent workflows._ ### Should I use STDIO, HTTP, or SSE transport for a GitHub Copilot CLI MCP server? Use STDIO for local processes Copilot launches on your own machine, and HTTP for remote, centrally hosted MCP services with header-based authentication. SSE is supported only for backwards compatibility and is described as deprecated in the MCP specification, so it should not be the default choice for new server configuration. _Developers picking transports for new MCP integrations can track guidance like this through daily.dev._ ### Is the GitHub MCP server already built into GitHub Copilot CLI or do I need to add it manually? The GitHub MCP server is built into GitHub Copilot CLI and works without any extra configuration, giving access to repository, issue, pull request, and GitHub context by default. Custom MCP servers should only be added for capabilities beyond that built-in GitHub surface, such as documentation lookup or browser automation, to avoid duplicating functionality already present. _daily.dev helps developers stay current on default agent tooling so they avoid redundant setup work._ ## Similar posts on daily.dev - [Github Copilot on the command line \(continued\)](https://daily.dev/posts/github-copilot-on-the-command-line-continued--vmgk0uvla) · The Art of Simplicity · 0 upvotes · 0 comments - [How to Build an Agentic Terminal Workflow with GitHub Copilot CLI and MCP Servers](https://daily.dev/posts/how-to-build-an-agentic-terminal-workflow-with-github-copilot-cli-and-mcp-servers-ihn9vqjsw) · freeCodeCamp · 5 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#ai-agents](https://daily.dev/tags/ai-agents), [#mcp](https://daily.dev/tags/mcp) [View this post on daily.dev](https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Using MCP Servers with GitHub Copilot CLI","url":"https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc"},"datePublished":"2026-07-25T11:57:01.320Z","dateModified":"2026-09-13T20:42:49.285Z","description":"GitHub Copilot CLI has the GitHub MCP server built in, so no extra configuration is needed for GitHub context. Custom MCP servers extend the CLI with docs...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/440992cd148684f3b19f7e10f5464732?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/440992cd148684f3b19f7e10f5464732?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"We Are .NET","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,ai-agents,mcp","timeRequired":"PT12M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"Using MCP Servers with GitHub Copilot CLI"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/using-mcp-servers-with-github-copilot-cli-yht9grxjc#faq","mainEntity":[{"@type":"Question","name":"How do I add a custom MCP server to GitHub Copilot CLI from the terminal?","acceptedAnswer":{"@type":"Answer","text":"Use the copilot mcp add command, putting the server command after a double dash for local STDIO servers, for example: copilot mcp add playwright -- npx -y @playwright/mcp@latest. For remote servers, add --transport http along with the URL. Additional flags include --env for environment variables, --header for HTTP headers, --tools to filter exposed tools, and --timeout for timing control. daily.dev surfaces practical CLI configuration guides for developers wiring MCP servers into their agent workflows."}},{"@type":"Question","name":"Should I use STDIO, HTTP, or SSE transport for a GitHub Copilot CLI MCP server?","acceptedAnswer":{"@type":"Answer","text":"Use STDIO for local processes Copilot launches on your own machine, and HTTP for remote, centrally hosted MCP services with header-based authentication. SSE is supported only for backwards compatibility and is described as deprecated in the MCP specification, so it should not be the default choice for new server configuration. Developers picking transports for new MCP integrations can track guidance like this through daily.dev."}},{"@type":"Question","name":"Is the GitHub MCP server already built into GitHub Copilot CLI or do I need to add it manually?","acceptedAnswer":{"@type":"Answer","text":"The GitHub MCP server is built into GitHub Copilot CLI and works without any extra configuration, giving access to repository, issue, pull request, and GitHub context by default. Custom MCP servers should only be added for capabilities beyond that built-in GitHub surface, such as documentation lookup or browser automation, to avoid duplicating functionality already present. daily.dev helps developers stay current on default agent tooling so they avoid redundant setup work."}}]} ```