# DingConnect MCP connector

The DingConnect connector lets Claude, ChatGPT, Cursor and the Elaichi Agent send and cancel mobile top-ups, estimate prices, look up accounts and bills, and check balances and provider status, each person acting within their own DingConnect access.

Source: https://elaichi.ai/connectors/dingconnect/

## Facts

| | |
| --- | --- |
| Application | DingConnect |
| Category | Payment Gateway |
| AI tools | 17 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once DingConnect is connected

- Estimate the price of a 10 dollar top-up to Nigeria
- List transfers sent this week and flag any that failed
- Which providers in Kenya are currently down?

## Connect DingConnect in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick DingConnect.
2. Optionally set Share with, then press Connect.
3. Paste your DingConnect app credentials. DingConnect authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which DingConnect tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## DingConnect MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## DingConnect MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## DingConnect MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect DingConnect to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a DingConnect tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with DingConnect through Elaichi

### Find a transfer the customer says never arrived

Support. Pull up the transfer records for a phone number, see the status and error code description in plain words, and give the customer an answer on the first contact.

### Send a top-up and confirm it landed

Operations. Look up the account, estimate the price, send the transfer, and read back the confirmation without switching between screens.

### Check balances before the morning batch

Finance. Ask for current balances across currencies and catch a low balance before transfers start failing for lack of funds.

### Compare products and promotions by country

Product. List the products and active promotions for a country or region, with their descriptions, and decide what to feature this week.

### Know which providers are down right now

Partnerships. Check provider status across the regions you cover and warn partners before their customers notice failed top-ups.

### Cancel a suspicious transfer and keep the record

Compliance. Cancel a transfer that looks wrong, then pull the full transfer records for that account so the review has everything in one place.

## Elaichi vs Zapier MCP vs Composio for DingConnect

All three can connect DingConnect to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over DingConnect tools | Allow or restrict single DingConnect tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per DingConnect call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect DingConnect to Claude?

Open DingConnect in the Elaichi catalog, choose connect, and sign in with your DingConnect app credentials. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. DingConnect is now available in your conversations.

### Does DingConnect work with ChatGPT and Cursor as well as Claude?

Yes. Once DingConnect is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect DingConnect once and every client picks it up.

### What can an AI agent actually do with my DingConnect data?

With DingConnect connected, an agent can look up an account or a bill, estimate the price of a top-up, send or cancel a transfer, and list past transfer records. It can also check balances, provider status, products, promotions, countries, regions and currencies, and explain an error code in plain words. Short concrete asks, like "estimate a 10 dollar top-up to this number", work better than long paragraphs.

### Does connecting DingConnect give the AI access to my whole account?

No. Every call to DingConnect runs under the access of the person who signed in, so an agent can only see and do what that person already can in DingConnect. Elaichi can narrow that access further, for example read-only on transfers, but it can never widen it.

### Can my team share one DingConnect connection?

Yes. One person connects DingConnect in Elaichi and shares it with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every transfer, lookup or cancellation.

### Can I stop an agent from deleting or changing things in DingConnect?

Yes. Restrictions in Elaichi apply per action, so you can allow lookups, price estimates and transfer records while blocking sending or canceling transfers. A restricted DingConnect action is never advertised to the AI client at all, so no prompt, however worded, can reach it.

### What happens to a DingConnect connection when someone leaves?

When you offboard someone in Elaichi, their access to DingConnect ends at once, in every client they used. A shared DingConnect connection keeps working for everyone else on the team. If you want DingConnect gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

### Does the DingConnect MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. DingConnect is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for DingConnect?

Yes. Both let Claude, ChatGPT or Cursor use DingConnect. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every DingConnect call.

### How is Elaichi different from Composio for DingConnect?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to DingConnect: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 17 DingConnect tools

Every tool below is callable through https://api.elaichi.ai/mcp once DingConnect is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a DingConnect cancel transfer** (Create). Cancel one or more DingConnect transfers in batch by submitting an explicit list of records to cancel (use ListTransferRecords first to find TransferIds available to cancel). Each result item reports the transfer's ProcessingState — 'Cancelled' means the transfer was successfully cancelled and balance compensations applied, any other state means it could not be cancelled. Returns per item:…
- **Create a DingConnect estimate price** (Create). Estimate send or receive prices for Ding products by submitting a batch of estimation requests. Returns per-item: Price (CustomerFee, DistributorFee, ReceiveValue, TaxRate), SkuCode, BatchItemRef, ResultCode, ErrorCodes. SendValue and ReceiveValue cannot both be non-zero.
- **List all DingConnect get account lookups** (List). Look up the provider and product information for a specific account number in DingConnect. Returns country, provider and region code details for the account number, ready to pass to GetProducts; typically a single entry, but can return multiple items, and returns an empty list when no match is found.
- **List all DingConnect get balances** (List). Get the current DingConnect agent balance, including any commission-on-sale increments but excluding transfers that are still processing. Returns the balance record with CurrencyIso and CurrencyName.
- **List all DingConnect get countries** (List). List the countries supported by Ding Connect, each with its ISO 3166-1 alpha-2 two letter code (XG is used for products available in all countries) and the country name in English. Returns: CountryIso, CountryName, InternationalDialingInformation, RegionCodes.
- **List all DingConnect get currencies** (List). List the ISO 4217 currencies supported by dingconnect. Returns each currency as a three-letter code with its English name: CurrencyIso, CurrencyName. Requires no parameters.
- **List all DingConnect get error code descriptions** (List). Get a list of error code descriptions in DingConnect: the human readable messages corresponding to the ErrorCodes returned in failed API responses. Returns items with: Code, Description. Messages are aimed at agents, not suitable for end-user display; new error codes may be added over time.
- **List all DingConnect get product descriptions** (List). List localized product descriptions in DingConnect, optionally filtered by product SKU codes and language codes. Returns each record's SkuCode, LocalizationKey, and Descriptions with the localized strings per language. English (en) is always included, and not all items have translations in every language.
- **List all DingConnect get products** (List). List Ding Connect products that can be used in SendTransfer, filterable by country, region, provider, SKU, benefit, and account number. Returns each product's SkuCode, ProviderCode, Minimum and Maximum prices, Benefits, ProcessingMode, RedemptionMechanism, SettingDefinitions, and UatNumber. Call GetProductDescriptions for localized product text.
- **List all DingConnect get promotion descriptions** (List). Get localized promotion description strings from DingConnect, each keyed to its promotion via LocalizationKey. Returns: Dates, Headline, TermsAndConditionsMarkDown, BonusValidity, PromotionType, LocalizationKey, LanguageCode, SendAmounts. Optionally filter by language_codes.
- **List all DingConnect get promotions** (List). List the Ding promotions that may apply for the submitted criteria. Returns promotion records with id and validity_period_iso (ISO8601 duration, e.g. P30D is 30 days). Localized promotion text is provided separately by the GetPromotionDescriptions endpoint.
- **List all DingConnect get providers** (List). List the DingConnect product providers available to the agent account, optionally filtered by provider codes, country ISOs, region codes, or an account number. Returns provider records including ProviderCode, Name, RegionCode, plus ValidationRegex, CustomerCareNumber, and LogoUrl where available. All query filters are optional; use international phone number format for phone-based account numbers.
- **List all DingConnect get provider status** (List). Get the current status of product providers in dingconnect to check whether it is possible to send a transfer to each one. Returns status entries including the agent-facing Message detail, which is unlocalized and not suitable for end users. Optionally filter with provider_codes.
- **List all DingConnect get regions** (List). List the regions used in the Ding Connect system. Returns: RegionCode, RegionName, CountryIso.
- **List all DingConnect list transfer records** (List). Query transfer records submitted by the agent in DingConnect. Returns: TransferRecord (with TransferId, SkuCode, Price, CommissionApplied, StartedUtc, CompletedUtc, ProcessingState, ReceiptText, ReceiptParams, AccountNumber), ResultCode, and ErrorCodes. Only transfers from the last 2 months are searchable. Required: Take.
- **Create a DingConnect lookup bill** (Create). Search available bills for an account in dingconnect before paying them via SendTransfer. Returns each matching bill's BillRef, Price (send/receive values, fees, tax), and AdditionalInfo. Only needed for products where LookupBillsRequired is true. Required: SkuCode, AccountNumber.
- **Create a DingConnect send transfer** (Create). Send a transfer to an account in DingConnect. Returns the created transfer record with TransferId, SkuCode, Price (send/receive values, fees, tax), ProcessingState, CommissionApplied, AccountNumber, and receipt details. SkuCode must come from GetProducts; transfers exceeding 90 seconds return ProviderTimedOut and are not charged. Required: SkuCode, SendValue, AccountNumber, DistributorRef, ValidateOnly.