How do I get a DingConnect API Key?

Log in to your DingConnect account and navigate to the developer portal or API settings section to generate or retrieve your unique API Key.

Can the agent perform actual top-ups?

This integration currently focuses on discovering operators, products, and auditing balance and history. Executing actual financial top-ups should be managed via the DingConnect portal or specialized integration.

Does the integration show real-time exchange rates?

Yes, when retrieving product pricing, the agent provides the latest rates and currency conversions as reported by the DingConnect platform.

DingConnect MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: DingConnect
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to DingConnect through Vinkius, pass the Edge URL in the `mcps` parameter and every DingConnect tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="DingConnect Specialist",
    goal="Help users interact with DingConnect effectively",
    backstory=(
        "You are an expert at leveraging DingConnect tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in DingConnect "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About DingConnect MCP Server

Integrate DingConnect, the world's leading mobile top-up platform, directly into your AI workflow. Access thousands of mobile operators globally, manage your top-up and data products, monitor real-time account balances, and track transaction history using natural language.

When paired with CrewAI, DingConnect becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call DingConnect tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Operator Discovery — List and search for mobile network operators across 150+ countries supported by DingConnect.
Product Intelligence — Access detailed information on available top-up and data plans, including technical keys and pricing.
Transaction Auditing — List and retrieve detailed history for past service executions and their status.
Balance Management — Track your account credit balance and organizational limits directly via chat.

The DingConnect MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect DingConnect to CrewAI via MCP

Follow these steps to integrate the DingConnect MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from DingConnect

Why Use CrewAI with the DingConnect MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with DingConnect through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

DingConnect + CrewAI Use Cases

Practical scenarios where CrewAI combined with the DingConnect MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries DingConnect for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries DingConnect, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain DingConnect tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries DingConnect against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

DingConnect MCP Tools for CrewAI (10)

These 10 tools become available when you connect DingConnect to CrewAI via MCP:

check_mobile_service_status

Check if mobile services are available for a specific destination (mock logic)

get_account_credit_balance

Retrieve the current credit balance for your DingConnect account

get_api_account_metadata

Retrieve metadata and settings for your DingConnect API account

list_available_topup_products

List all available top-up and data products for a specific provider

list_mobile_operators

List all mobile network operators (providers) for a specific country

list_supported_countries

List all countries supported by DingConnect for mobile services

list_top_volume_countries

Identify countries with high service availability (mock logic)

list_transaction_history

List recent top-up transactions and service history

quick_operator_audit

Retrieve a high-level summary of operators and products for a country

search_topup_products

Search for specific top-up or data products by name keyword

Example Prompts for DingConnect in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with DingConnect immediately.

"List all mobile operators available in Brazil."

"What is my current account credit balance?"

"Show me the top-up plans for operator 'Safaricom' in Kenya."

Troubleshooting DingConnect MCP Server with CrewAI

Common issues when connecting DingConnect to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

DingConnect + CrewAI FAQ

Common questions about integrating DingConnect MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.