Answer: You can reuse your VS Code MCP configuration by finding your MCP settings in your repository's .vscode/mcp.json file or your machine's private settings.json file, then adapting them for repository MCP settings on GitHub: add a tools key for each MCP server, switch inputs and envFile to use env directly, and update references to inputs in args to refer to environment variables from env. Status: Confirmed Entry: tool/github-copilot/integrations/reuse-vscode-mcp-config Revision: 2 Digest: sha256:d76b44ae01d60e07 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:26:27Z Last changed: 2026-11-19T12:59:45Z (Alternative config file location: — → settings.json) Last verified: 2026-11-20T13:06:03Z Next check: 2026-11-21T13:06:03Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of VS Code config file location | .vscode/mcp.json | [1] | 2026-11-20 Alternative config file location | settings.json | [1] | 2026-11-20 Required key per server | tools | [1] | 2026-11-20 Replace inputs with | env | [1] | 2026-11-20 Replace envFile with | env | [1] | 2026-11-20 Update args references | env | [1] | 2026-11-20 Sources: [1] GitHub. "Configure MCP servers for your repository - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers Role: primary. Accessed: 2026-11-20T13:06:03Z Quote: "you may be able to find your MCP settings in your repository's .vscode/mcp.json file" (Supports: VS Code config file location) Quote: "or in your machine's private settings.json file" (Supports: Alternative config file location) Quote: "Add a tools key for each MCP server, specifying which tools will be available to Copilot." (Supports: Required key per server) Quote: "If you've configured inputs , switch to using env directly." (Supports: Replace inputs with) Quote: "If you've configured an envFile , switch to using env directly." (Supports: Replace envFile with) Quote: "Update any references to inputs in your args configuration to refer to environment variables from env instead." (Supports: Update args references) Snapshot SHA-256: 0afe028814fcd51c5c403c5a63b0098fe72dc23a38c039d3b37781d64c589d72 (captured 2026-11-18T13:00:49Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:00:50Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:06:03Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:06:03Z Last attempt: 2026-11-20T13:06:03Z Notes and limitations: Extracted automatically from a single official source (section "Reusing your MCP configuration from Visual Studio Code"). Related: https://latestn.com/tool/github-copilot/integrations/sdk-authentication How do I authenticate the GitHub Copilot SDK in my application? https://latestn.com/tool/github-copilot/integrations/sdk-server-to-server-auth How do I set up server-to-server authentication for the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/integrations/sdk-server-to-server-auth-github-actions How do I configure server-to-server authentication for the GitHub Copilot SDK in GitHub Actions? https://latestn.com/tool/github-copilot/integrations/mcp-servers-sdk How do I use MCP servers with the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/integrations/per-repository-mcp-servers How do I add a per-repository MCP server in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/integrations/plugin-json-fields What fields can I set in a plugin.json manifest for GitHub Copilot CLI plugins? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:59:45Z | changed | Alternative config file location: — → settings.json | [1] 2026-11-19T12:59:45Z | changed | Alternative config file: settings.json → — | [1] 2026-11-13T03:26:27Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/integrations/reuse-vscode-mcp-config/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/integrations/reuse-vscode-mcp-config POST: https://latestn.com/dispute/tool/github-copilot/integrations/reuse-vscode-mcp-config with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/integrations/reuse-vscode-mcp-config?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How can I reuse my MCP configuration from Visual Studio Code in GitHub Copilot? Revision 2, last verified 2026-11-20T13:06:03Z. https://latestn.com/tool/github-copilot/integrations/reuse-vscode-mcp-config (accessed 2026-11-21T10:00:26Z). @misc{LatestN_tool_github_copilot_integrations_reuse_vscode_mcp_config_r2, title = {How can I reuse my MCP configuration from Visual Studio Code in GitHub Copilot?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/integrations/reuse-vscode-mcp-config}}, note = {Revision 2; digest sha256:d76b44ae01d60e07; last verified 2026-11-20T13:06:03Z; accessed 2026-11-21T10:00:26Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/integrations/reuse-vscode-mcp-config