Connect Dify to IPMusk

Who this is for

People who build agents and workflows in Dify, on Dify Cloud or self-hosted, and want them to read IPMusk usage and build proxy URLs.

What you need

• An IPMusk account with a verified email address.
• For the MCP server: no API key. Dify signs in to IPMusk for you and you choose the permissions in your browser. Tick read and connect for typical use.
• For the custom tool: an IPMusk API key with read and connect. Add support or order only if the agent should open tickets or create orders.
• 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.
• 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: MCP server

1. 1
   Add the server

   In Dify, open Tools → MCP and choose Add MCP Server (HTTP).

2. 2
   Enter the details

   Set the server URL to https://ipmusk.com/mcp, the name to IPMusk and the server ID to ipmusk. Save.

3. 3
   Sign in and approve

   Dify registers itself and opens the IPMusk sign-in page. Sign in, tick read and connect, then choose Approve.

4. 4
   Use the tools

   The IPMusk tools appear on the card. Add them to an agent or a workflow.

https://ipmusk.com/mcp

If the tools stop working later, choose Re-authorize on the IPMusk card.

Set it up: custom tool from OpenAPI

1. 1
   Create a custom tool

   In Dify, open Tools → Custom and choose Create.

2. 2
   Import the schema

   Choose to import from URL and paste the OpenAPI URL below.

3. 3
   Add your key

   Set Authentication to API Key, the header to Authorization, the prefix to Bearer and the value to your IPMusk key. Save.

https://ipmusk.com/api/v1/openapi.json

Everyone who can use this tool in your Dify workspace acts with your key. Give it only the scopes they need.

Check it works

MCP server: the IPMusk card under Tools → MCP lists the tools. In an agent that has them, ask: Which IPMusk account am I connected as?

Custom tool: test the me_get tool in the tool editor. It should return your email address.

Try these prompts

• How much residential traffic do I have left on IPMusk?
• Give me a rotating residential proxy URL for Germany.
• List my Static ISP proxies and when they expire.

If it fails

• The IPMusk sign-in page says the request is not valid: delete the MCP server in Dify and add it again.
• The tools stop working after a while: choose Re-authorize on the IPMusk card.
• The custom tool returns 401: the key is wrong or revoked, or the prefix is not Bearer.
• 403 forbidden on one tool: you did not grant that permission. Disconnect the app in Settings → API keys → Connected AI apps, connect again and tick the permission.
• 403 capability_unavailable: the customer API is switched off on this deployment. Contact support.

Remove access

• Go to Settings → API keys → Connected AI apps (/app/settings/api-keys) and choose Disconnect next to the app. It stops working at once.
• Then delete the IPMusk server under Tools → MCP in Dify.
• For a custom tool, revoke its key in Settings → API keys and delete the tool.