VS Code with GitHub Copilot

Get your instance’s MCP URL from your administrator or Connect a client in the console. See connection prerequisites and sign-in before starting.

These screenshots show the VS Code Agents interface provided in September 2026. Use GitHub Copilot for this flow. Available options can depend on your VS Code version and organization settings.

1. Open the Agents window

In VS Code, select Open in Agents in the title bar. The Windows shortcut shown is Ctrl+Shift+A.

VS Code title bar showing Open in Agents

Under Customizations, select MCP Servers.

Agents window with an arrow pointing to MCP Servers

2. Add the HTTP server

Click the + button beside Browse Marketplace to add a server.

MCP Servers page with the Add Server plus button

Choose HTTP (HTTP or Server-Sent Events) from the server types. This is VS Code’s label for the remote HTTP option; Cutova uses Streamable HTTP.

Server type picker with an arrow pointing to HTTP

Paste your complete MCP URL and press Enter. The ABCD quick code in the screenshot is an example; use the URL for your own instance.

Enter Server URL prompt with an example Cutova MCP URL

Enter a server ID such as Cutova MCP for Epicor Kinetic and press Enter.

Enter Server ID prompt with a Cutova name

Choose Global to make the configuration available across your workspaces, or Workspace to keep it scoped to the current workspace. The example selects Global.

Configuration target picker with Global selected and Workspace available

VS Code asks whether the MCP server may authenticate to the Cutova server. Check the server you just added, then click Allow.

VS Code permission dialog asking to authenticate to the Cutova server

Your browser opens the sign-in flow. Sign in to your own Epicor environment using your normal account and sign-in method.

Example Epicor sign-in screen

On the Epicor MCP Auth screen, review the notice and click Authorize.

Epicor MCP Auth screen with the Authorize button

4. Approve the VS Code connection in Cutova

Cutova then shows Authorize access to Epicor. Check the signed-in user, environment, application and destination before clicking Allow access.

In this example, the application is Visual Studio Code and the destination is a local address such as http://127.0.0.1:33418. This returns sign-in to VS Code on your computer. The port can vary; do not copy this example address into your MCP server settings.

Cutova consent screen identifying Visual Studio Code and its local callback destination

Approve only the connection you started and recognize. For Epicor Classic’s token-paste flow, see the shared sign-in guide.

The browser confirms Sign-in successful! Returning to Visual Studio Code…. Return to VS Code. If it does not redirect automatically, use the page’s link or close that sign-in page.

Browser page confirming successful sign-in and return to Visual Studio Code

5. Check the server and try a tool

Confirm Cutova appears in MCP Servers.

VS Code MCP Servers list containing Cutova MCP for Epicor Kinetic

Return to your Copilot session and try a first tool call using a tool enabled for your instance. Review any tool permission prompt before continuing.

Epicor® and Kinetic® are trademarks of Epicor Software Corporation. Cutova is an independent product and is not affiliated with, endorsed by, or sponsored by Epicor Software Corporation.

Cutova, a product of Lens Software LLC