Agent guides

Connect Cursor to IPMusk

Add IPMusk to Cursor's mcp.json. Cursor's agent can then read your account and build proxy URLs while it codes.

Who this is for

Developers who use Cursor and want its agent to fetch proxy URLs and account details.

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.
  • The key in an environment variable named IPMUSK_API_KEY, for example export IPMUSK_API_KEY="ipm_live_YOUR_KEY" in your shell profile. The examples below read it from there.
  • Cursor installed.

Set it up

Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects.

  • ${env:IPMUSK_API_KEY} reads the key from your environment, so the file is safe to commit.
  • Start Cursor from a shell where IPMUSK_API_KEY is set, or set it in your shell profile.
  • Without headers, Cursor may offer to sign in with OAuth instead. If that sign-in fails, use the key.
.cursor/mcp.json
{
  "mcpServers": {
    "ipmusk": {
      "url": "https://ipmusk.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:IPMUSK_API_KEY}"
      }
    }
  }
}

Check it works

Open Cursor Settings → MCP. ipmusk should show a green dot and its tools.

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

  • Red dot or no tools: open the server's log in Settings → MCP. A 401 means Cursor could not read IPMUSK_API_KEY.
  • 401 authentication_required: the key is missing, wrong, revoked or expired. Check that IPMUSK_API_KEY is set where the client starts. echo ${#IPMUSK_API_KEY} prints its length without showing the key.
  • 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.
  • Changes do not show: toggle the server off and on in Settings → MCP, or restart Cursor.

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.