---
title: "Connect the MCP to GitHub Copilot"
url: "https://academy.visuresolutions.com/en/article/connect-the-mcp-to-github-copilot"
language: "en"
last_updated: "2026-09-02T19:51:42.901Z"
---

# Connect the MCP to GitHub Copilot

Requires **Node.js** (nodejs.org). (Complete the MCP prerequisites first.) There are two ways to configure it, plus certificate troubleshooting.

### Through the Desktop App

1.  In Copilot, go to **Settings > MCP Server**.
2.  Click **\+ Add server** → **\+ Add custom server**. ![](https://cdn-assets.productfruits.com/373c3c15-86ea-4918-b676-7ed04218de19)
3.  Fill in the form:
4.  -   **Server name:** `visure`
    -   **Command:** `npx`
    -   **Arguments:** `-y mcp-remote` `https://WWW.YOURDOMAIN.COM/VisureAuthoring8/mcp` (use your installation's URL)
    -   **Environment variable:** `MCP_TIMEOUT: 180000` ![](https://cdn-assets.productfruits.com/2349d0ee-8173-4074-ae96-15eef68feb22)
5.  Save, then return to **Settings > MCP Server** and enable the MCP.
6.  You'll be redirected to the Visure Authoring login page.

### Through the configuration file

Edit `mcp-config.json` — Mac: `/Users/<YourUsername>/.copilot/`, Windows: `C:\Users\<YourUsername>\.copilot\` — and add:

json

```
{
  "mcpServers": {
    "visure": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@^0.1.43",
        "https://your-host/VisureAuthoring8/mcp"
      ],
      "env": {
        "MCP_TIMEOUT": "180000"
      }
    }
  }
}
```

Launch Copilot, go to **Settings > MCP Server**, and enable the MCP. You'll be redirected to the Visure login page. ![](https://cdn-assets.productfruits.com/c0daf68e-792c-4479-96db-ea4843fd5ca9)

### Troubleshooting a self-signed certificate

If you get **HTTP error 405** or a **connection-refused timeout**, an IIS self-signed certificate is likely the cause. Export it as a Base64 `.cer` from IIS Manager and reference it with `NODE_EXTRA_CA_CERTS`:

1.  In IIS Manager, select **Default Web Site** → **Bindings**. ![](https://cdn-assets.productfruits.com/9310a46e-20d2-4b29-88d8-348ae27a9e34)
2.  Edit the **https** binding, select the certificate from the SSL dropdown, click **View**.
3.  On the **Details** tab, **export the certificate without the private key**.![](https://cdn-assets.productfruits.com/c7534c43-82c7-4797-aefa-3ce53301f12f)
4.  Copy the `.cer` to a known path (e.g. `C:\self_signed_localhost.cer`).![](https://cdn-assets.productfruits.com/f6917c36-9d5f-4262-a326-58850140f9b5)![](https://cdn-assets.productfruits.com/bdc990c0-8961-4a66-b33e-f63ac4e96c12)
5.  Add it to the config:

json

```
"env": {
  "MCP_TIMEOUT": "180000",
  "NODE_EXTRA_CA_CERTS": "C:/self_signed_localhost.cer"
}
```

(You can also add `NODE_EXTRA_CA_CERTS` directly in Copilot's MCP settings.) You should now connect with your self-signed certificate. ![](https://cdn-assets.productfruits.com/ccfcc808-7805-4f18-ae62-c215ef45ef6c)
