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.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
17 tools
How to connect
How to connect DingConnect to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect DingConnect once
-
Open Connections, choose Add connection, and pick DingConnect.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
DingConnect MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect DingConnect to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with DingConnect through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Find a transfer the customer says never arrived
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.
-
Operations
Send a top-up and confirm it landed
Look up the account, estimate the price, send the transfer, and read back the confirmation without switching between screens.
-
Finance
Check balances before the morning batch
Ask for current balances across currencies and catch a low balance before transfers start failing for lack of funds.
-
Product
Compare products and promotions by country
List the products and active promotions for a country or region, with their descriptions, and decide what to feature this week.
-
Partnerships
Know which providers are down right now
Check provider status across the regions you cover and warn partners before their customers notice failed top-ups.
-
Compliance
Cancel a suspicious transfer and keep the record
Cancel a transfer that looks wrong, then pull the full transfer records for that account so the review has everything in one place.
Try asking
- “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?”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
DingConnect tools for your AI agents
17 tools are ready to call through Elaichi's MCP endpoint the moment you connect DingConnect, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting DingConnect gets you
6 screens from the product, each doing one job for your DingConnect account.
The agent
Ask about transfers and balances in plain language.
Three starter prompts pull live DingConnect transfer records, balances and provider status into one answer.
- transfers
- products
- providers
- balances
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches DingConnect from every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
17 DingConnect tools, no code to write.
Transfers, products, providers, balances, promotions and bill lookups, cataloged and ready without a line of code.
- Create a DingConnect cancel transfer
- Create a DingConnect estimate price
- List all DingConnect get account lookups
- List all DingConnect get balances
ElaichiToolsToolboxes
Every team gets its own DingConnect toolbox.
Support looks up accounts, Finance watches balances, and each toolbox is scoped to its team.
- Support
- Operations
- Finance
- Product
ElaichiToolboxesShared connections
Teammates send transfers without seeing a credential.
One person connects DingConnect, shares it with teams, and the table shows who has access.
- Support
- Finance
- Operations LATAM
- Partnerships
ElaichiConnectionsAudit log
Every DingConnect transfer is traced to a person.
When, who, what happened, type and resource, recorded for each call in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Scheduled runs turn transfer records into digests.
Transfer records are fetched, grouped, drafted into a digest, approved by a person, then posted back.
DingConnect digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch transfers
DingConnect
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
DingConnect
Queued
Collections and dashboards
Transfer health, computed on a schedule.
Four metrics, 14 days of transfers created and a breakdown by team, with no model involved.
DingConnect health
Refreshed 4 minutes ago · every 15 minutes · from the transfers collection
Transfers
1,284 ↓ 12%
Products
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Transfers created
Last 14 days
By team
Share of activity
Support 34%
Finance 27%
Operations LATAM 21%
Partnerships 18%
FAQ
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 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.
Put DingConnect in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.