VS Code + GitHub Copilot
Connect VS Code + GitHub Copilot to Noxgild, verify protected tool access, and run a real task.
Give GitHub Copilot access to the environment around the repo: the computer, long-running processes, signed-in browser, and native apps.
Setup tutorial
1. Install VS Code and sign in to Copilot
- Download and open Visual Studio Code, then sign in to the GitHub account that has Copilot access.
- Open the project you want Copilot to work with, and select Agent mode in Copilot Chat.
2. Open VS Code's MCP setup
- Press Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS.
- Run the exact Command Palette action “MCP: Add Server” and choose HTTP (Streamable HTTP) as the server type.
- If asked where to save it, choose User Configuration for all projects or Workspace Configuration for only this project.
3. Enter and enable the Noxgild server
- Paste this URL when asked for the remote HTTP endpoint; name the server noxgild.
- Review the trust prompt, then enable/start noxgild from the MCP Servers list if necessary.
- User config is in your VS Code profile; workspace config is .vscode/mcp.json.
https://mcp.noxgild.com/mcp4. Authorize Noxgild
- When VS Code prompts you to sign in, open the browser authorization and approve Noxgild.
- Return to VS Code; make sure the server and tools are enabled in Copilot Chat's tool picker.
5. Test Noxgild in Copilot Chat
- In Copilot Chat, keep Agent mode selected and allow the Noxgild tool call.
- A successful test lists your authorized computer and its current status. ONLINE means the device is available; an authorized connection alone is not a test.
Use the connected Noxgild MCP server only. Call noxgild_devices and list my available computers and their current status.Before you start
- VS Code with GitHub Copilot and MCP support.
Noxgild MCP endpoint
https://mcp.noxgild.com/mcpVerification prompt
Send this to your AI client after setup:
Use the connected Noxgild MCP server only. Call noxgild_devices and list my available computers and their current status.After authorization, send the verification prompt. You are connected when your authorized computer and its status appear.
Good first tasks
- Run this branch on my QA computer and verify the fix in the signed-in browser.
- Start the development server, keep it running, and inspect its output while I continue coding.
- Open the native desktop build and verify the UI change.
Troubleshooting
- If Noxgild tools do not appear, reload the VS Code window and check that the noxgild MCP server is enabled.
- If authorization looks stale, reconnect the Noxgild server from VS Code and authorize again.
Connect a computer once
If you do not already have an authorized Windows, macOS, or Linux computer in Noxgild, run this in a terminal on that Windows, macOS, or Linux computer:
npx @noxgild/cli@latest connectAfter approval, the same computer can be reused from other supported AI clients.
