Bring African Payments
to Cursor
Learn how to connect Tingg Insights to Cursor 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 Cursor?
Cursor's Agent mode turns Tingg Insights into an in-editor superpower. Ask Cursor to generate code using live data from Tingg Insights and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Tingg Insights in Cursor
Tingg Insights and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Tingg Insights to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.