MCP Connectors canvas gives Copilot agents managed access to external tools without manual configuration

MCP Connectors canvas gives Copilot agents managed access to external tools without manual configuration

Microsoft has shipped the MCP Connectors canvas, a plugin for the GitHub Copilot app that connects agents to external services through hosted MCP servers in Azure Connector Namespace. Rather than manually configuring an MCP server—finding an endpoint, editing configuration, managing auth headers and token lifetimes—a developer browses a list of published servers and selects one.

Connector Namespace is a managed Azure service that hosts curated MCP servers, stores and rotates credentials, applies retry and throttling policies, and scales the servers. Access is governed by namespace access policies, which give admins control over who can use a particular server. The canvas, an extension installed at personal scope, lists those servers inside the Copilot app and registers them in the user-scoped MCP configuration file at ~/.copilot/mcp-config.json. The documented walkthrough involves signing into Azure in the canvas, browsing servers grouped under Microsoft and Partners, and completing the connector's separate consent or authentication flow.

There is no local MCP proxy between the agent and the server. The canvas runs on loopback, Azure tokens stay in process memory, and gateway credentials go only to the server's configured HTTPS endpoints. Connector secrets never touch the developer's machine; Connector Namespace manages them, so an admin can rotate or revoke a connection centrally instead of updating per-developer configuration files.

Because the GitHub Copilot app is built on GitHub Copilot CLI, a server connected in the canvas also shows up in the terminal. copilot mcp list lists it, and /mcp show SERVER-NAME lists the exposed tools. The connection is user-scoped, so any session picks it up regardless of repository or branch.

Tools load when a Copilot session starts, so a server added mid-session only appears in the next session; the documentation advises restarting. Project-level .mcp.json or .github/mcp.json files take precedence over user config on name collisions. VS Code differs: Copilot Chat there reads .vscode/mcp.json, a separate file the CLI doesn't use, so a canvas connection won't appear until separately configured.

The canvas extension format carries no compatibility guarantee from GitHub, so an app update might require a matching plugin update. Connector Namespace remains in preview with regional availability varying. Deleting a connection from the namespace affects any other developer sharing it.

The GitHub Copilot app went generally available in June 2026, and the canvas shipped with it. Connector Namespace has not reached general availability; it remains in preview.