Connecting VS Code to the DevOps Loop MCP server
You can connect Visual Studio Code (VS Code) with GitHub Copilot to connect to the DevOps Loop MCP Server. After configuration, Copilot can run MCP-based queries to retrieve and update loop resources directly from VS Code. The MCP server connection is saved and remains available across sessions.
Before you begin
- Ensured that you have installed VS Code and the GitHub Copilot extension.
- Obtained the MCP Server URL. For example:
https://hostname/loop/mcp
About this task
Procedure
-
Perform the following steps by using the command palette:
-
Open VS Code.
-
Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P).
-
Search and select Copilot: Add Server
-
Choose HTTP as the server type, when prompted for the transport type.
-
The DevOps Loop MCP Server uses HTTP-based transport.
-
-
Enter the MCP Server URL, in the URL field.
VS Code automatically generates the required
mcp.jsonconfiguration. -
Enter a name for the server. For example: Loop MCP Server.
-
Select Workspace, when VS Code prompts you to choose where to save this configuration.
-
Global – used for all VS Code workspaces
-
Workspace – used only in the current folder/project
Note: Selecting Workspace automatically creates a.vscodefolder and generates amcp.jsonfile inside it.
-
- Click Extensions icon
and navigate to . - Click the Settings icon
next to Loop MCP Server. -
Select Start server option.
VS Code displays a notification stating that the MCP server requires authentication.
- Click Allow to proceed.
A second notification is displayed asking whether you want to open an external website.
- Click Open.
Your default browser opens and displays the DevOps Loop login page.
-
Sign in with your DevOps Loop credentials.
A consent screen is displayed requesting access to MCP tools, loop APIs, and basic profile information.
- Click Yes to approve and complete the connection.
After successful authentication, VS Code displays the list of available MCP tools. See MCP tools available in DevOps Loop.
Note: The MCP server times out after 30 minutes of inactivity. If no tool calls occur during this period, your session will expire and you will be prompted to re-authenticate. -
-
Perform the following steps to manually modify the MCP configuration
file:
-
Open VS Code.
- Open any empty directory or project in VS Code.
- Create a new folder named
.vscodeinside that directory, if not present. - Create a file named
mcp.jsoninside the.vscodefolder. - Paste the MCP configuration JSON. For
example:
{ "servers": { "loop-mcp": { "uri": "https://hostname/loop/mcp", "type": "http" } }, "inputs": [] }Replace the
hostnamewith your actual DevOps Loop server hostname. - Save the file.
- Click Extensions icon
and navigate to . - Click the Settings icon
next to Loop MCP Server. -
Select Start server option.
VS Code displays a notification stating that the MCP server requires authentication.
- Click Allow.
A second notification appears asking whether you want to open an external website.
- Click Open.
Your default browser opens and displays the DevOps Loop login page.
- Sign in with your DevOps Loop
credentials.
A consent screen is displayed requesting access to MCP tools, loop APIs, and basic profile information.
- Click Yes to approve and complete the connection.
After successful authentication, VS Code displays the list of available MCP tools. See MCP tools available in DevOps Loop.
Note: The MCP server times out after 30 minutes of inactivity. If no tool calls occur during this period, your session will expire and you will be prompted to re-authenticate. -
