Who this is for
Developers who use iFlow CLI (心流), Alibaba's coding agent for the terminal, and want it 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.
- iFlow CLI installed.
- IPMusk applies the same source-country rules to the API and MCP as to the website, so connect from a region where ipmusk.com is available.
Set it up
Run this once in your terminal.
- Use double quotes so the shell expands $IPMUSK_API_KEY.
- The server is saved in ~/.iflow/settings.json. Servers for one project live in .iflow/settings.json in that project.
- The key ends up in the settings file. Do not commit it.
- If you edit settings.json by hand, run /mcp refresh inside iFlow CLI to load the change.
iflow mcp add --transport http ipmusk https://ipmusk.com/mcp --header "Authorization: Bearer $IPMUSK_API_KEY"Check it works
Run iflow mcp list in your terminal, or /mcp list inside iFlow CLI. ipmusk 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
- 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.
- The header shows a literal $IPMUSK_API_KEY: you used single quotes. Delete the ipmusk entry and add it again with double quotes.
- 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 to settings.json do not show: run /mcp refresh, or restart iFlow CLI.
Remove access
- Revoke the key in Settings → API keys (/app/settings/api-keys). It stops working at once.
- Then delete the ipmusk entry from settings.json and run /mcp refresh.