Set up VS Code GitHub Copilot using Remote OAuth
Scenario
Use this procedure to connect GitHub Copilot in Visual Studio Code to the OvalEdge Remote MCP Server via OAuth. This configuration enables GitHub Copilot to securely access OvalEdge MCP tools through browser-based authentication without storing OvalEdge credentials in the local configuration file.
Steps Involved
In Visual Studio Code, press Ctrl + Shift + P to open the Command Palette, type MCP: Open User Configuration, and select it.

The mcp.json configuration file opens. Add the Remote MCP OAuth configuration under the servers section using the Remote MCP endpoint URL and OAuth callback port.
{ "servers": { "ovaledge-remote-oauth": { "type": "http", "url": "https://YOUR_PUBLIC_MCP_BASE_URL/mcp", "oauth": { "callbackPort": 8790 } } } }Save the mcp.json file after adding the configuration.
Press Ctrl + Shift + P, type Developer: Reload Window, and select it to reload Visual Studio Code and apply the updated MCP configuration.

Press Ctrl + Shift + P, type MCP: List Servers, and select it.

Select the ovaledge-remote-oauth server from the list.

Select Start Server to start the configured Remote MCP server.

When the MCP server starts, a confirmation dialog appears indicating it wants to authenticate. Click Allow.

If not already signed in to Okta, the user navigates to the Okta sign-in page. Enter the Okta credentials and complete the sign-in process.

If already signed in to Okta, authentication proceeds directly, and a browser popup prompts opening Visual Studio Code 2. Click Open Visual Studio Code 2 to return to Visual Studio Code and complete the authentication.

Verify that the Output panel displays a message similar to Discovered 25 tools, confirming that the MCP server has started successfully.

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?

