Connect to Copilot Studio MCP with Visual Studio Code and GitHub Copilot CLI

Add Copilot Studio MCP to Visual Studio Code or GitHub Copilot CLI by using the Microsoft-published npm package. Your client launches the server with npx and communicates with it over stdio. Sign in and select an environment to access the connected service's tools.

Prerequisites

  • Complete Configure access to Copilot Studio MCP, including Node.js, npm, and npx availability where the server runs.
  • For Visual Studio Code, install a supported version with GitHub Copilot chat and MCP access.
  • For GitHub Copilot CLI, install a supported version of GitHub Copilot CLI.
  • Confirm that your organization permits the @microsoft/copilot-studio-mcp package.

You don't need to clone the public documentation repository or configure a remote MCP URL.

Visual Studio Code

Install from the registry

  1. Open the Extensions view and search for @mcp copilot-studio.

  2. Select the Microsoft Copilot Studio MCP listing and review its publisher, package, and installation requirements.

  3. Select Install, or use Install in Workspace if you need workspace-scoped configuration.

  4. Review the configuration and server trust prompt before you start the server.

You can also find the server in the GitHub MCP Registry and use its Visual Studio Code installation option when available. The public repository's README supplies the server documentation. npm supplies the runnable package.

Configure the server manually

As an alternative to registry installation, add this configuration to .vscode/mcp.json:

{
  "servers": {
    "copilot-studio-mcp": {
      "command": "npx",
      "args": ["-y", "@microsoft/copilot-studio-mcp@latest"]
    }
  }
}

Merge the entry into any existing servers object rather than overwriting unrelated servers. To use user-profile scope instead, run MCP: Open User Configuration.

Start the server by using the Visual Studio Code MCP controls and review the trust prompt. npx retrieves and launches the package. It doesn't grant Copilot Studio permissions or authorize business operations. The -y option accepts npm's package-fetch prompt, not client trust, authentication consent, or tool-action approvals. @latest uses npm's current latest release. Use an approved fixed version if your organization requires version pinning.

Visual Studio Code also supports portable configuration with a top-level mcpServers object, including a workspace .mcp.json file. Use the schema for your destination. GitHub Copilot CLI doesn't read the Visual Studio Code-specific .vscode/mcp.json file.

Learn more in Add and manage MCP servers in VS Code.

Use the tools in chat

  1. Open a chat mode that supports tools and enable the Copilot Studio MCP tools.

  2. Begin with this request:

    Connect to Copilot Studio MCP and show my available environments so I can choose one. Don't create, publish, run, or repair anything.

  3. Complete browser sign-in and choose the intended environment.

  4. After you connect, refresh the available tools if prompted, and then try this request:

    Show the Copilot Studio MCP capabilities available in this connection and confirm the target environment. Don't change anything.

GitHub Copilot CLI

Add the server interactively

  1. Start GitHub Copilot CLI.

  2. Enter /mcp add.

  3. Set Server Name to copilot-studio-mcp.

  4. Set Server Type to STDIO or Local. These options launch a process, unlike the HTTP option.

  5. Set Command to npx -y @microsoft/copilot-studio-mcp@latest.

  6. Review which tools you want to enable, following your organization's policy. Enabling tools doesn't replace approval for consequential actions.

  7. Press Ctrl+S to save.

Servers added this way are available without restarting the CLI. Complete sign-in and environment selection before you use the connected service's tools.

Add the server from the terminal

As an alternative to the interactive form, register the local server from the terminal:

copilot mcp add copilot-studio-mcp -- npx -y @microsoft/copilot-studio-mcp@latest

This command adds the server to your user configuration. It doesn't grant service permissions, create a connector connection, or authorize a deployment.

Configure the server manually

For user-level configuration on Windows, edit %USERPROFILE%\.copilot\mcp-config.json in the default configuration location:

{
  "mcpServers": {
    "copilot-studio-mcp": {
      "type": "local",
      "command": "npx",
      "args": ["-y", "@microsoft/copilot-studio-mcp@latest"],
      "tools": ["*"]
    }
  }
}

Merge with existing entries. If you use a custom configuration home, use that location instead. The tools setting makes the advertised tools available to the client. It doesn't approve every action they can perform.

For project-scoped settings, follow the client's documented configuration and workspace-trust requirements. Learn more in Adding MCP servers for GitHub Copilot CLI.

Confirm the connection

Use /mcp to inspect the registered server. Review its state and available tools, and then use the connection request in the Use the tools in chat section to sign in and choose an environment. Reuse an already-ready connection rather than signing in again.

For broader tasks, see Use Copilot Studio MCP and the example requests.

Troubleshoot the client connection

Symptom Action
npx isn't found Check that Node.js and npm are installed and available on the PATH used by the MCP client. In remote development, check the machine or container that runs the server.
npm can't retrieve the package Confirm the exact Microsoft package name and approved npm and network access.
The server isn't in the registry Confirm that the listing is available in your client's configured registry. Use manual configuration if the npm package is permitted.
Configuration isn't recognized Check the file location and top-level object: servers for Visual Studio Code-specific configuration, mcpServers for the portable and CLI format.
The server is disabled or blocked Review client trust, enabled tools, and organizational server policies. Don't bypass policy to connect.
Authentication can't complete Check account, consent, and browser sign-in requirements. Don't paste a token into chat as a workaround.
Only connection tools appear Complete sign-in and environment selection, and then refresh tool discovery by using the client's supported controls.
The response is interrupted Inspect the operation's known state before you retry. A client interruption might not cancel server-side work.

Use the client's server-management controls to stop, disable, or remove the registration when needed. This action doesn't delete Copilot Studio artifacts or reverse previous changes.

  • Last updated on