Skip to main content

Connect VS Code to Floxar

You use Floxar in VS Code from GitHub Copilot Chat in agent mode. VS Code identifies itself to Floxar with its own Client ID Metadata Document, so you enter no client ID or secret. The connection is confirmed with VS Code 1.139, the desktop editor.

Before you start, make sure MCP is on for your account and have your account URL ready. Connecting an AI client explains both, and what the sign-in and consent page show.

Add Floxar​

  1. Add the server to .vscode/mcp.json in your workspace. If the file already lists servers, add only the Floxar entry inside the existing servers object. Or run MCP: Add Server from the Command Palette, choose HTTP, paste your account URL and give it a name for the account.

    {
      "servers": {
        "acme-floxar": {
          "type": "http",
          "url": "https://mcp.floxar.com/a/<account_id>"
        }
      }
    }

  2. Start the server. When VS Code asks to let Floxar sign in, allow it, then sign in to Floxar, confirm the account and allow the connection.

  3. Open Copilot Chat in agent mode. Floxar's tools appear in the tools picker.

What the sign-in looks like​

The consent page shows VS Code under Floxar's label for it. VS Code runs on your computer, so the connection returns to a local address, and the consent page says so.

Known limits​

  • VS Code stays connected. Floxar renews its access whether or not VS Code asks to stay connected, because its registration allows it.
  • Signing out in VS Code is local only. It discards VS Code's access, but the connection stays active in Floxar until you or an account admin end it there (see "Disconnecting and revoking" in Connecting an AI client).
  • The desktop editor only. VS Code for the Web, in the browser, is not a supported way to connect and is expected to be refused.
  • More than one account. Give each account's entry its own name; a second entry with the same name in mcp.json replaces the first.

Last reviewed: 2026-09-30