Connect an AI coding tool to the developer MCP

The DHRU developer MCP is a public, read-only reference for building integrations. It provides Fusion Pro supplier and reseller APIs, order callbacks and custom payment gateway guidance, plus PayerOne integration references and the Dhru Fusion API standards. It cannot access your workspace or merchant account, place orders, move funds or confirm a payment.

Add the server

In an AI coding tool that supports remote MCP over Streamable HTTP, add a server with the URL https://www.dhru.com/mcp. Choose no authentication when your client asks. This public reference does not require sign-in, an API key or an Authorization header. Follow your client's current instructions for adding a remote HTTP MCP server.

Example: Claude Code

With Claude Code installed, run:

claude mcp add --transport http dhru-developers https://www.dhru.com/mcp
claude mcp get dhru-developers

Check the connection status before using the tools. See Claude Code's remote MCP instructions for current client setup details.

Find the contract and starter code

Ask your AI coding tool to follow this sequence:

  1. Call list_integrations first. Use product: "fusion-pro" to narrow the list to Fusion Pro.
  2. Call get_integration with the returned integration id, such as fusion-reseller-api. Read the setup, requests, replies and rules before writing code.
  3. Call get_code_sample with integration: "fusion-reseller-api". It lists the available samples; call it again with an available language, such as node, php or python. Availability varies by integration.
  4. Call validate_payload with the integration ID to discover its supported checks. Then supply the selected kind and a JSON-string payload containing fictional values and placeholders. Review reported errors and warnings.

A prompt to try

"Use the DHRU developer MCP to help me build a Fusion Pro reseller integration in Node.js. Start with list_integrations, then read fusion-reseller-api and fusion-order-callback using get_integration. Get the available Node.js starter code with get_code_sample. List the supported validate_payload checks and check a fictional example. Use YOUR_API_KEY and YOUR_TOKEN wherever a credential would be needed. Do not ask for secrets or send any live orders."

Keep credentials and customer data private

Never paste API keys, tokens, passwords, private keys or real customer records into a prompt or payload sent to this public server. Use placeholders such as YOUR_API_KEY and YOUR_TOKEN. Configure real credentials privately in your application's environment when you are ready to integrate. Payload validation checks the documented format and rules; it does not contact your account, verify a webhook signature or prove that an order or payment succeeded. Review generated code and test it in an appropriate test environment before live use.

Choose the connection for your task

Use this public developer MCP for documentation and coding help. To let an AI app work with your own Fusion Pro workspace, use the separate, authenticated Settings → Connected AI connection and the permissions you approve. Follow Connect an AI app with OAuth and manage its access. PayerOne account access also uses a separate authenticated connection; see Connect an AI client with MCP. A connection to the public developer reference does not authorize access to either account.

If the connection does not work

Confirm the URL is exactly https://www.dhru.com/mcp and the client supports remote Streamable HTTP MCP. Refresh or reconnect the server and ask it to list its tools again. If the client requests credentials for this public reference, review the server URL and client configuration instead of sharing a secret. You can also start from the DHRU Developers overview and its public integration links.