Skip to content

Connect Copilot to braXos

braXos Maestro works with GitHub Copilot in Visual Studio Code as a remote MCP server. Setup takes a couple of minutes and a single browser sign-in; Copilot registers itself with the braXos identity service automatically, so there is nothing to pre-provision.

Before you start

  • A braXos account in your organization. Your administrator confirms which systems and tools are enabled for you.
  • Visual Studio Code with the GitHub Copilot and GitHub Copilot Chat extensions, signed in to GitHub.
  • On a Copilot Business or Enterprise plan, your GitHub organization must allow MCP: the MCP servers in Copilot policy is off by default. Ask your GitHub administrator if the steps below don't offer MCP servers.
  • Your organization's Maestro URL, e.g. https://maestro.braxos.com/mcp.

Add braXos Maestro

  1. Open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows/Linux) and run MCP: Add Server.
  2. Choose HTTP.
  3. Paste your Maestro URL, e.g. https://maestro.braxos.com/mcp.
  4. Name it braxos-maestro.
  5. Choose Global to use it in every workspace, or Workspace to keep it in this project's .vscode/mcp.json.

The resulting configuration is:

{
  "servers": {
    "braxos-maestro": {
      "type": "http",
      "url": "https://maestro.braxos.com/mcp"
    }
  }
}

Sign in

  1. Open Copilot Chat, switch to Agent mode, and send a message - for example "What braXos tools do I have?". Copilot starts the server on the first message.
  2. VS Code asks to authenticate braxos-maestro. Allow it; your browser opens the braXos sign-in.
  3. Sign in with your organization's identity provider (single sign-on where configured).
  4. Review the consent screen and approve. It lists Offline access, which lets Copilot keep your session alive without asking you to sign in again (see below).
  5. Back in VS Code, the Configure Tools picker in the chat input lists the braXos tools available to you.

Authentication

Copilot authenticates with OAuth 2.0 against the braXos identity service, exactly as Claude does: you sign in as yourself, Maestro derives your organization and group memberships from your token, and the tools you can see and call are filtered by your group permissions. Credentials for the downstream systems (Google, Jira, Salesforce, …) stay server-side and are never exposed to Copilot or the model.

Staying signed in. Copilot holds an offline refresh token, so it renews access in the background and you should not be asked to sign in again day to day. Your administrator can revoke it at any time, and removing you from your organization cuts access immediately.

See Security & tenancy for the full model.

Using braXos tools

  • Copilot asks before running a tool. Read-only tools are marked as such; actions that change data (provisioning, sending, deleting) always ask for confirmation.
  • Tool limits. Copilot caps the number of tools it can send per request (about 128). If your organization enables more than that, use Configure Tools to turn off the braXos tools you don't need for the task at hand.
  • Picking up new tools. When your access grows (a connector is enabled or you're added to a group), start a new chat, or restart the server from MCP: List Servers.

Troubleshooting

Symptom Likely cause Fix
Server shows Error with no output right after VS Code starts Copilot hasn't created its chat session yet ("Send a message first" in the logs) Send any message in Copilot Chat; the server starts with it
Sign-in page says Client not found VS Code reused a client registration that no longer exists Run Authentication: Remove Dynamic Authentication Providers, remove the braXos entry, then restart the server
Asked to sign in again repeatedly An older connection without offline access Remove the dynamic authentication provider (above), restart the server, and approve Offline access on the consent screen
Server connects but shows no tools No tools enabled for your groups Ask your braXos administrator to grant access
A tool call fails with a permissions message The call was blocked before reaching braXos, or your group lacks access Retry once; if it persists, contact your braXos administrator with the time of the call

Logs. MCP: List Servers → braxos-maestro → Show Output shows the server's own messages. Sign-in and startup messages are in Developer: Show Logs… → Window; search for braxos-maestro.

Other Microsoft Copilot surfaces

This guide covers GitHub Copilot in VS Code. Microsoft 365 Copilot and Copilot Studio require a pre-registered connection rather than automatic sign-up; contact braXos if you need them.