Bring African Payments
to CrewAI
Learn how to connect Tingg Insights to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Tingg Insights MCP Server?
Connect your Tingg (Cellulant) payments account to any AI agent and simplify how you collect payments, manage disbursements, and track financial settlements across Africa through natural conversation.
What you can do
- Transaction Oversight — List and search all payment transactions and retrieve real-time status for specific checkout requests.
- Disbursement Control — Initiate and monitor payouts (B2C/B2B) to recipients across supported mobile money and bank channels.
- Settlement Tracking — List bank settlements to monitor when funds are moved from your Tingg account to your local bank.
- Payment Initiation — Programmatically create new checkout requests to collect payments via mobile money, card, or bank.
- Engagement Automation — Send transactional SMS or Email notifications to users via the Tingg Engage service.
- Performance Metrics — Retrieve high-level account metrics and payment success rates to monitor your business health.
How it works
1. Subscribe to this server
2. Enter your Tingg Client ID and Client Secret (found in your merchant portal)
3. Start managing your African payment ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Finance & Operations Managers — quickly check transaction statuses and verify bank settlements via simple AI commands.
- E-commerce & Business Owners — monitor payout progress and retrieve account performance metrics directly from the workspace.
- Product Teams — automate payment requests and trigger user notifications via the AI assistant.
Built-in capabilities (12)
Verify Tingg API connectivity
Initiate a new payment request
Retrieve performance stats
Check status of a payout
Check status of a specific transaction
Request a refund
Send money to a recipient
List bank settlements
List active webhooks
List all payouts/disbursements
List recent payment transactions
Send SMS or Email alert
Why CrewAI?
When paired with CrewAI, Tingg Insights becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Tingg Insights tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Tingg Insights in CrewAI
Tingg Insights and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Tingg Insights to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Tingg Insights in CrewAI
The Tingg Insights 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Tingg Insights for CrewAI
Every tool call from CrewAI to the Tingg Insights MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the status of a specific payment request via AI?
Yes! Use the get_transaction_status tool and provide the Checkout Request ID. Your agent will retrieve the real-time payment status from Tingg.
How do I see my latest bank settlements?
Run the list_account_settlements query. The agent will retrieve a list of all funds that have been settled from your Tingg account to your linked bank account.
Is it possible to send money to a recipient (payout) via AI?
Absolutely. Use the initiate_payout_request action. Provide the payout details including amount, currency, and recipient info in the JSON payload to start the disbursement.
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.
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.