Connect VS Code

Use LeadsAgent from VS Code and GitHub Copilot.

Set up with your AI assistant

Where you use VS Code

Paste the prompt into VS Code. It includes setup steps and a read-only connection check.

VS Code — VS Code editor: sign in with LeadsAgent (recommended)

Copilot agent mode in the VS Code desktop editor.

Click “Install in VS Code” at the top of this page and confirm in VS Code. Or add it by hand: open the Command Palette (Ctrl+Shift+P, or Cmd+Shift+P on a Mac) and run “MCP: Add Server”.
If adding by hand: choose “HTTP”, paste the URL, and enter leadsagent as the server ID. Current versions offer workspace .mcp.json or Copilot Global configuration; choose the scope you want. Older editor-only configurations use a different format.
Server URL
```
https://leadsagent.io/mcp/v1
```
Review the trust prompt. Then sign in with your LeadsAgent account in the browser and approve access.
Open the Chat view and ask for leads. Use “Configure Tools” in the chat input to switch individual LeadsAgent tools on or off.

VS Code — VS Code editor: use an API key

On the LeadsAgent setup page, select “Create an API key”. Name it for this app and set its expiry and limits. Copy it once; it starts with la_.
Set LEADSAGENT_API_KEY in the environment used by this app. Restart the app so it reads the variable. Keep the value out of chats and shared files.
Terminal
```
LEADSAGENT_API_KEY
```
For current Copilot harnesses, merge this into workspace .mcp.json or the user’s $COPILOT_HOME/mcp-config.json (fallback ~/.copilot/mcp-config.json). Confirm your installed version supports environment expansion in headers. Portable configuration uses mcpServers.
.mcp.json · Copilot harness
```
{
  "mcpServers": {
    "leadsagent": {
      "type": "http",
      "url": "https://leadsagent.io/mcp/v1",
      "headers": {
        "X-API-Key": "${LEADSAGENT_API_KEY}"
      }
    }
  }
}
```

For editor-only setup, use MCP: Open User Configuration or .vscode/mcp.json. This format uses servers and can ask for the key securely. Interactive input variables are not forwarded into Copilot harness sessions.

.vscode/mcp.json · editor only

{
  "inputs": [
    {
      "type": "promptString",
      "id": "leadsagent-key",
      "description": "LeadsAgent API key",
      "password": true
    }
  ],
  "servers": {
    "leadsagent": {
      "type": "http",
      "url": "https://leadsagent.io/mcp/v1",
      "headers": {
        "X-API-Key": "${input:leadsagent-key}"
      }
    }
  }
}

Run “MCP: List Servers”, select leadsagent and start it. Complete any trust prompt and, for the editor-only variant, the key prompt.

VS Code — Copilot CLI: use an API key

The copilot command in a terminal. It stores servers in ~/.copilot/mcp-config.json. Remote sign-in is not documented for the Copilot CLI, so use an API key.

The Copilot CLI stores header values as plain text. Keep ~/.copilot/mcp-config.json private.

On the LeadsAgent setup page, select “Create an API key”. Name it for this app and set its expiry and limits. Copy it once; it starts with la_.
Add the server. Replace la_your_key with your key in your own terminal; do not paste it into a chat.
Terminal
```
copilot mcp add --transport http --header "X-API-Key: la_your_key" leadsagent https://leadsagent.io/mcp/v1
```
Or, inside the Copilot CLI, type /mcp add, fill in the fields with Tab and press Ctrl+S to save.
In Copilot CLI
```
/mcp add
```
Ask Copilot to check your LeadsAgent account.

Source: VS Code docs: add and manage MCP servers · Open in Connectors