Skip to main content
plugin

connector-namespaces — GitHub Copilot plugin for MCP servers

Browse and connect hosted MCP servers from an Azure Connector Namespace in a GitHub Copilot canvas. Use it to manage connections and inspect servers in the namespace playground.

Install into GitHub Copilot · Command from the source All methods and platforms ↓
copilot plugin install connector-namespaces@awesome-copilot
Open on GitHub

What connector-namespaces does

The plugin adds an interactive canvas to the GitHub Copilot side panel. Browse or search Microsoft and partner MCP servers available in an Azure Connector Namespace, then sign in to Azure, select a subscription and namespace, and complete each connector’s authentication or consent in your browser. Connected servers appear under My MCPs. Restart the GitHub Copilot app afterward so the agent can use their tools.

You need access to an Azure subscription with a Connector Namespace, permission to view it and create connections and hosted MCP server configurations, and a browser for Microsoft Entra sign-in and connector consent. Azure sign-in and connector sign-in are separate. Azure tokens stay in the extension process, so signing in again is required after an app restart. Connector Namespace is an Azure preview service, and availability can vary by region.

What it helps with

  • find an MCP server in the Azure Connector Namespace catalog
  • connect a server and complete its browser authentication
  • check which MCP servers are connected to Copilot
  • open a connected server in the namespace playground

Example prompts for the agent

  • Open the MCP Connectors canvas and connect a server from the Azure Connector Namespace catalog.
  • Sign in to Azure, choose a subscription and namespace, then check the connected servers under My MCPs.
  • Open a connected server in the Connector Namespace playground.

How to install connector-namespaces

Command from the source

copilot plugin install connector-namespaces@awesome-copilot

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about connector-namespaces

How do I install connector-namespaces in GitHub Copilot?

Run copilot plugin install connector-namespaces@awesome-copilot.

What does connector-namespaces do?

It adds a GitHub Copilot canvas for finding and connecting hosted MCP servers from an Azure Connector Namespace. You can also manage connected servers there.

What does connector-namespaces require?

You need an Azure subscription with a Connector Namespace, permission to manage its connections and hosted server configurations, and a browser for Microsoft Entra sign-in and connector consent. Connector Namespace preview availability varies by region.

Source text

connector-namespaces · MIT
# MCP Connectors

A GitHub Copilot app canvas extension for discovering and connecting hosted MCP
servers from [Azure Connector Namespace](https://learn.microsoft.com/en-us/azure/connector-namespace/connector-namespace-overview).
It brings the Microsoft and partner connector catalog, guided browser sign-in,
and connected-server management into the Copilot side panel.

## Features

- **Connector catalog** - browse and search Microsoft and partner MCP servers
  available in your namespace.
- **Guided Azure setup** - sign in from the canvas, then choose a subscription
  and Connector Namespace.
- **Browser-based connection flow** - complete each connector's authentication
  or consent without leaving the setup experience.
- **My MCPs** - see which servers are connected and ready to add to Copilot.
- **Namespace playground** - open any connected server in the Connector
  Namespace playground with **Sandbox**.
- **Persistent namespace selection** - retain the selected namespace while Azure
  tokens remain in memory and sign-in is requested again after a restart.

## Install

Install the standalone `connector-namespaces` plugin from the Azure Connectors
marketplace:

```bash
/plugin marketplace add Azure/Connectors
/plugin install connector-namespaces@Azure-Connectors
```

## Requirements

- Access to an Azure subscription with a Connector Namespace. If you do not
  have one, follow the
  [Connector Namespace creation guide](https://learn.microsoft.com/en-us/azure/connector-namespace/create-connector-namespace).
- Permission to view the namespace and create its connections and hosted MCP
  server configurations.
- A browser for Microsoft Entra sign-in and connector consent.

Connector Namespace is currently an Azure preview service and availability can
vary by region.

## Usage

1. Open the **MCP Connectors** canvas in the GitHub Copilot app.
2. Select **Sign in to Azure** and complete Microsoft Entra authentication in
   your browser.
3. Choose an Azure subscription and Connector Namespace.
4. Browse or search the catalog, then select **Connect** on an MCP server.
5. Complete the connector's sign-in or consent flow when prompted.
6. Confirm the server appears under **My MCPs**.
7. Restart the GitHub Copilot app so the new tools become available to the
   agent.

Use **Sandbox** on a connected server to inspect it in the Connector Namespace
playground. Use **Change namespace** to switch subscriptions or namespaces.

## Authentication and privacy

Azure sign-in and connector sign-in are separate:

- **Azure sign-in** lets the canvas discover and manage Connector Namespace
  resources. Access and refresh tokens remain in the extension process and are
  never written to extension files. Reloading the extension or restarting the
  app requires Azure sign-in again. The selected namespace coordinates are
  retained in
  `~/.copilot/extensions/connector-namespaces/artifacts/gateway-config.json` so
  the canvas can explain that the namespace is still linked and return directly
  to its connectors after sign-in.
- **Connector sign-in** grants an individual MCP server access to its backing
  service. The resulting connection is managed by Connector Namespace.

The canvas serves its interface from loopback only (`127.0.0.1`). Azure
management requests are restricted to `https://management.azure.com/`.
The gateway API key that lets Copilot reach a connected server is stored in the
user-scoped GitHub Copilot MCP configuration and sent only to that server's
configured HTTPS endpoint.

## Development

The maintainable source, tests, and pinned build tooling live in this plugin
folder. The private `package.json` is only a reproducible build workspace; this
plugin is not published as an npm package. The installable extension is
generated at `extensions/extension.mjs`, matching Awesome Copilot's external
canvas intake convention.

```bash
npm ci
npm run build
npm run check
```

The bundle includes `@azure/identity` and its pure-JavaScript dependencies.
Node built-ins and `@github/copilot-sdk/extension` remain external because the
runtime supplies them. Do not edit the generated bundle or third-party notices
directly.

## Release

The **Release MCP Connectors canvas** GitHub Actions workflow rebuilds and tests
the extension from an exact `main` commit, then publishes a
`connector-namespaces-canvas@<version>` release. Its generated awesome-copilot
descriptor pins this plugin directory to both the release tag and immutable
commit SHA.

## License

[MIT](./LICENSE) © Microsoft Corporation.

© Microsoft · MIT · Azure/Connectors

Similar plugins

All plugins for Cloud: AWS, Azure, GCP →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor