Who this is for
Developers who use Baidu Comate (文心快码) 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.
- 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.
- Comate installed, in a version with MCP support.
- 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
Add the server to ~/.comate/mcp.json for all projects, or to .comate/mcp.json in your workspace.
- Replace ipm_live_YOUR_KEY with your key. If you use the workspace file, add .comate/mcp.json to .gitignore.
- Parts of Comate's manual write transportType instead of type. Try type first; if the server does not start, rename it to transportType.
- If you also set requestInit.headers, Comate merges both header lists. Spell Authorization the same way in both, or keep only one.
{
"mcpServers": {
"ipmusk": {
"type": "streamableHttp",
"url": "https://ipmusk.com/mcp",
"headers": {
"Authorization": "Bearer ipm_live_YOUR_KEY"
}
}
}
}Check it works
Open Comate's MCP settings, or reload the window. ipmusk should be listed with 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
- 401 authentication_required: the key in the file is wrong, revoked or expired. Paste it again without extra spaces.
- The server does not start: check the JSON is valid, then try transportType in place of type.
- 401 although the key is right: two Authorization headers with different casing were merged. Keep one.
- 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.
- Then delete the ipmusk entry from mcp.json.