Connect VS Code / GitHub Copilot
Connect VS Code with GitHub Copilot to HeadlessOps via MCP
Connecting VS Code / GitHub Copilot
VS Code with the GitHub Copilot extension supports MCP servers in Agent mode (VS Code 1.99+).
Prerequisites
- VS Code 1.99 or later
- GitHub Copilot extension installed and active
- A HeadlessOps account with at least one workspace
Option A: Remote MCP (Recommended)
Add the following to your VS Code settings.json:
User settings (Ctrl+Shift+P → Preferences: Open User Settings (JSON)):
{
"mcp": {
"servers": {
"headlessops": {
"url": "https://app.headlessops.ai/mcp",
"type": "http"
}
}
}
}Or as a workspace-level config in .vscode/mcp.json:
{
"servers": {
"headlessops": {
"url": "https://app.headlessops.ai/mcp",
"type": "http"
}
}
}- Save the file
- Open GitHub Copilot Chat and switch to Agent mode
- Authorize in the browser when prompted
Option B: Local Proxy (Enables folderPath)
Install the local proxy to enable folderPath support for reading and writing local integration files.
Step 1 — Install the Proxy
npm install -g @headlessops-ai/mcpStep 2 — Configure VS Code
In settings.json or .vscode/mcp.json:
{
"mcp": {
"servers": {
"headlessops": {
"type": "stdio",
"command": "headlessops-mcp",
"args": ["--mcp-url", "https://app.headlessops.ai/mcp"]
}
}
}
}Or without a global install using npx:
{
"mcp": {
"servers": {
"headlessops": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@headlessops-ai/mcp", "--mcp-url", "https://app.headlessops.ai/mcp"]
}
}
}
}macOS Homebrew Node: Use
/opt/homebrew/bin/headlessops-mcpas thecommandif VS Code doesn't inherit your shell PATH.
Workspace Resolution
Create iterator/iterator.config.json in your project root:
{ "workspaceId": "ws_abc123" }To find your workspace ID, ask Copilot: "List my HeadlessOps workspaces"
Example Prompts
Open GitHub Copilot Chat in Agent mode (@workspace or #mcp) and try:
- "List all my HeadlessOps integrations"
- "Show the last 5 runs of the crm-sync integration"
- "Create a scheduled integration that runs every weekday at 8am"
- "The invoice-processor failed — read the logs and fix the error"