How to Use Vibium MCP with GitHub Copilot

To use Vibium with GitHub Copilot, register Vibium's built-in MCP server in VS Code, then switch Copilot Chat to Agent mode and ask it to perform a browser task. Copilot calls the Vibium MCP tools to open a real browser and act — no glue code. Vibium's MCP server is the same one used by Claude Code and Cursor, so the workflow is familiar.

What is MCP, and how does Copilot use it?

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools. GitHub Copilot in VS Code supports MCP servers, and Vibium exposes one out of the box — so Copilot can drive a browser the same way it edits files or runs the terminal.

Ask vs Edit vs Agent mode

Copilot Chat has three modes, and only Agent mode runs tools like Vibium:

• Ask — answer questions about your code or Vibium APIs.
• Edit — propose multi-file edits you review and accept.
• Agent — autonomously plan, call tools (including the Vibium MCP server), run them, and iterate until the task is done.

Register the Vibium MCP server

VS Code reads MCP servers from an mcp.json file (workspace .vscode/mcp.json or your user profile). The general shape is:

{
  "servers": {
    "vibium": {
      "command": "<vibium-mcp-server-command>"
    }
  }
}

⚠️ The exact server command depends on your Vibium version. Confirm it in the official Vibium MCP docs before pasting it in.

Reload VS Code, open Copilot Chat, and confirm the vibium server appears in the tools list.

Run your first scenario with Copilot Agent

Switch Copilot Chat to Agent mode and prompt:

"Open example.com, take a screenshot, and tell me the main heading."

Copilot will call the Vibium MCP tools to launch the browser, capture the screenshot, read the page, and report back — then you can ask it to write that flow into a test file.

Next steps

• Set up Vibium MCP in Claude Code
• Set up Vibium MCP in Cursor
• What is Vibium?