Skip to main content

Connect Enrow to VS Code (GitHub Copilot)

Add Enrow to VS Code in one click or from a terminal, then sign in with your Enrow account.

Written by Thomas Lucy

To use Enrow in VS Code, add the Enrow server in one click from the Enrow app, then sign in to your Enrow account the first time GitHub Copilot uses it. You don't need an API key. You need VS Code 1.101 or later, with GitHub Copilot in agent mode.

Connect VS Code

  1. In Enrow, go to Integrations in the left menu, click the MCP tab, then click Connect on the VS Code card.

  2. Click Open in VS Code. VS Code opens with Enrow ready to install: click Install.

  3. Open Copilot Chat in agent mode and send this test prompt: "Use Enrow to check my credit balance."

  4. The first time Copilot uses Enrow, VS Code asks you to authenticate. Click Allow.

  5. Your browser opens. Sign in to Enrow if asked, then click Allow. The answer in Copilot Chat shows your balance. Reading your balance uses no credits.

The VS Code guide in Enrow, with the Open in VS Code button

To check that Enrow is running, open the Command Palette and run MCP: List Servers. enrow should show as running.

Add Enrow from a terminal

Instead of steps 1 and 2, run this command. Then follow steps 3 to 5.

code --add-mcp '{"name":"enrow","type":"http","url":"https://mcp.enrow.io/mcp"}'

Note: If you belong to an Enrow team and you are not its owner, you can't sign in from apps on your computer. Connect VS Code with your team's API key instead: see Connect any other MCP client.

If something goes wrong

  • The sign-in page says the request has expired. A sign-in request is valid for 10 minutes. Start the sign-in again from VS Code.

  • Enrow stopped working or asks you to sign in again. The access was disconnected in Enrow, or it expired. Sign in again from VS Code, the same way.

  • Enrow says a paid plan is required or a limit is reached. See Use Enrow in an AI assistant (MCP): overview.

To remove VS Code's access, go to Profile > Applications in Enrow and click Disconnect. Removing Enrow from VS Code is not enough: the access stays active in Enrow until you disconnect it.

Related articles

Did this answer your question?