Connecting Noibu to GitHub Copilot in VS Code

Last updated: October 16, 2026

This guide connects GitHub Copilot Chat in VS Code to your Noibu data, so Copilot can look up your site's errors, sessions, conversion and page performance while it works in your code. Setup is one prompt and takes about 5 minutes.

Using an older setup? GitHub Copilot used to be two extensions: GitHub Copilot and GitHub Copilot Chat. They are now unified into GitHub Copilot Chat, and the separate GitHub Copilot extension is deprecated. If your team still has both, update VS Code and GitHub Copilot Chat to the latest version before you start.

Before you start

You'll need:

  • VS Code with the GitHub Copilot Chat extension installed and signed in to GitHub.

  • Your Noibu login. You'll sign in once during setup.

  • Your site's domain as it's set up in Noibu (for example, www.example.com).

  • Copilot Business or Enterprise only: your GitHub org admin needs the MCP servers in Copilot policy turned on. It's off by default, and Noibu won't connect until it's on.

Step 1: Run the setup prompt

  1. Open the folder you work in with VS Code.

  2. Open Copilot Chat and set the mode to Agent.

  3. Open Noibu-GitHub-Copilot-Setup-Prompt.txt, copy its full contents, paste them into the chat and send.

Noibu-GitHub-Copilot-Setup-Prompt.txt

Copilot asks for your domain and whether you want Noibu set up for this repo only or globally for every workspace. Then it:

  • Adds the Noibu connection to VS Code.

  • Saves your site's details so Copilot knows which Noibu domain to use.

  • Adds a /noibu prompt for asking questions about your site.

  • Turns on the VS Code settings these need.

It asks before changing anything that already exists. Approve its file edits and terminal commands when prompted.

Step 2: Start the server and sign in

Two steps stay with you, because VS Code needs a person to do them:

  1. Click Start on the Noibu server. Copilot tells you where.

  2. Sign in to Noibu in the browser window that opens.

Then reply "done" and Copilot confirms the connection and finishes setup.

Try it

In Copilot Chat (Agent mode), type /noibu followed by your question, for example:

  • /noibu What are our top priority errors this week?

  • /noibu Which pages have the slowest load times on mobile?

  • /noibu How did conversion rate change over the last 30 days?

If you chose "this repo only", you can also ask in plain language without /noibu. Copilot picks up your site's details automatically in that workspace.

Good to know

  • Agent mode only. Noibu tools don't run in Ask or Edit mode.

  • Some Noibu features are built for Claude. Copilot gets Noibu's data tools. Guided workflows like /tech-diagnosis and in-chat session replays won't run in Copilot. Describe what you want in plain language instead, or use /noibu.

  • Everyone signs in as themselves. Each teammate connects with their own Noibu login.

Manual install

If you'd rather not use the setup prompt:

  1. Open the Command Palette (Cmd+Shift+P or Ctrl+Shift+P) and run MCP: Add Server.

  2. Choose HTTP, paste https://mcp.noibu.com/mcp and name it noibu.

  3. Click Start above the noibu entry in mcp.json, then click Allow and sign in to Noibu.

  4. Open Copilot Chat in Agent mode and include your site's domain in your questions.

Troubleshooting

  • Copilot can't see the Noibu tools. Click the tools icon in the chat box and make sure the noibu tools are checked, or start a new chat in Agent mode.

  • The sign-in prompt never appears. Check that the MCP policy is enabled for your org (see Before you start).

  • Something else isn't working. Click the gear icon in the top right of the Copilot Chat panel, go to MCP Servers, click the ... next to noibu and choose Show Output to see what's going on. You can also reach out to your Noibu contact and we'll help you get set up.