Who this is for
Developers who use the Zed editor and its agent panel.
What you need
- An IPMusk account with a verified email address.
- An API key with read and connect, or no key if you sign in with OAuth. Add support or order only if you want them.
- 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.
- Zed installed.
Set it up
Open Zed's settings.json and add the server. Zed uses a top-level context_servers key, not mcpServers.
- Replace ipm_live_YOUR_KEY with your key. settings.json is your user file. Do not commit it.
- Leave out headers to sign in with OAuth. Zed opens the IPMusk sign-in page in your browser.
{
"context_servers": {
"ipmusk": {
"url": "https://ipmusk.com/mcp",
"headers": {
"Authorization": "Bearer ipm_live_YOUR_KEY"
}
}
}
}Check it works
Open Settings → AI → MCP Servers (or the Agent panel settings). ipmusk should show as active.
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
- 401 authentication_required: the key is wrong, revoked or expired.
- The server is not listed: check that context_servers is at the top level of settings.json.
- 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.
Remove access
- Revoke the key in Settings → API keys (/app/settings/api-keys). It stops working at once.
- If you signed in with OAuth, disconnect Zed in Settings → API keys → Connected AI apps.
- Then delete the ipmusk entry from settings.json.