Connect Gummble MCP to GitHub Copilot

Add Gummble as a remote MCP server in VS Code or GitHub Copilot CLI for UI research.

Connect Gummble to local GitHub Copilot workflows when you want Copilot to research real screens, flows, UI patterns, and microcopy before it writes UI code.

This guide covers custom remote MCP setup in VS Code and Copilot CLI. It does not imply a GitHub Marketplace app, MCP Registry listing, partnership, or endorsement.

VS Code with GitHub Copilot

Run MCP: Add Server from the Command Palette, choose an HTTP server, enter the endpoint below, and choose whether to install it in your user profile or workspace:

https://mcp.gummble.com/mcp

Or add Gummble to .vscode/mcp.json:

{
  "servers": {
    "gummble": {
      "type": "http",
      "url": "https://mcp.gummble.com/mcp"
    }
  }
}

Start the server and confirm that you trust its configuration. When the server requires authentication, use the Auth action above the server in mcp.json and complete Gummble's browser OAuth flow. Do not hardcode a client secret, API key, or bearer token.

Open Copilot Chat in Agent mode and verify with:

Use Gummble to find three web checkout screens with express-payment
options. Return the source links and compare their information hierarchy
before changing the code.

GitHub Copilot CLI

Add the user-scoped remote HTTP server:

copilot mcp add --transport http gummble https://mcp.gummble.com/mcp

Run copilot mcp list to inspect status. If Gummble reports needs-auth, start Copilot CLI and run:

/mcp auth gummble

Complete the browser flow. Copilot CLI stores MCP configuration in ~/.copilot/mcp-config.json; it does not read VS Code's .vscode/mcp.json.

GitHub.com cloud-agent limitation

Copilot cloud agent and Copilot code review do not currently support remote MCP servers that use OAuth. Use Gummble in local VS Code or Copilot CLI, not those GitHub.com surfaces, until GitHub documents OAuth support.

Review the read-only MCP tool list before approving calls. GitHub documents that remote servers are low-trust and their tool calls require explicit permission.

Troubleshooting

If VS Code does not open OAuth, use the Auth CodeLens action above the server configuration.
If Copilot CLI reports needs-auth, run /mcp auth gummble again.
For plan, OAuth, scope, or tool-discovery failures, see MCP troubleshooting.

Review Gummble MCP access and connect your account.

Official GitHub references: MCP in VS Code, Copilot CLI MCP, Copilot CLI command reference, and cloud-agent MCP limitations.

Connect Gummble MCP to GitHub Copilot

VS Code with GitHub Copilot

GitHub Copilot CLI

GitHub.com cloud-agent limitation

Troubleshooting

On this page