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.
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
4. Save, then return to Settings > MCP Server and enable the MCP.
5. 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.

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.
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.
4. Copy the .cer to a known path (e.g. C:\self_signed_localhost.cer).
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.