Agent guides

Connect VS Code to IPMusk

Add IPMusk to VS Code's mcp.json. VS Code asks for your key once, stores it securely, and Copilot's agent mode can use the tools.

Who this is for

Developers who use VS Code with GitHub Copilot in agent mode.

What you need

  • An IPMusk account with a verified email address.
  • An IPMusk API key. Create it in Settings → API keys (/app/settings/api-keys). For typical use tick read and connect. Add support only if the assistant should open tickets, and order only if it should create orders that end in a payment link.
  • This client takes the key itself rather than reading the IPMUSK_API_KEY environment variable the other guides use. Keep the original in a password manager.
  • VS Code with GitHub Copilot, and MCP allowed in your Copilot settings or by your organisation.

Set it up

Create .vscode/mcp.json in your project. VS Code uses a top-level servers key, not mcpServers.

  • The first time the server starts, VS Code asks for the key and stores it. The file holds no secret.
  • To use it in every workspace, run MCP: Open User Configuration from the Command Palette and add the same block there.
.vscode/mcp.json
{
  "inputs": [
    {
      "id": "ipmusk-key",
      "type": "promptString",
      "description": "IPMusk API key",
      "password": true
    }
  ],
  "servers": {
    "ipmusk": {
      "type": "http",
      "url": "https://ipmusk.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:ipmusk-key}"
      }
    }
  }
}

Check it works

Open Copilot Chat in agent mode and click the tools icon. The IPMusk tools should be listed.

Ask the assistant: Which IPMusk account am I connected as? It should call get_account and answer with your email address.

Try these prompts

  • How much IPMusk residential traffic do I have left?
  • Get a sticky US proxy URL for 10 minutes and use it in this script.
  • List my IPMusk Static ISP proxies and when they expire.

If it fails

  • No prompt for the key: click Start above the server in mcp.json, or run MCP: List Servers and start ipmusk.
  • 401 after a key change: run MCP: Reset Cached Tools or remove the stored input, then start the server again.
  • 403 forbidden on one tool: the key lacks that tool's scope, or your email is not verified. Scopes cannot be added to a key, so create a new key with the scope and swap it in.
  • 429 rate_limited: too many calls in one minute (read 60, connect 20, support 30, order 10). Wait a minute and try again.
  • MCP is disabled: your organisation's Copilot policy may block MCP servers.

Remove access

  • Revoke the key in Settings → API keys (/app/settings/api-keys). It stops working at once.
  • Then delete the ipmusk entry from mcp.json.