Tingg Insights MCP Server for CursorGive Cursor instant access to 12 tools to Check Api Health, Create Checkout Request, Get Account Performance Metrics, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Tingg Insights app connector for Cursor is a standout in the Productivity category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Tingg Insights and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"tingg-insights": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 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.
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.
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.
The Tingg Insights MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 Tingg Insights tools available for Cursor
When Cursor connects to Tingg Insights through Vinkius, your AI agent gets direct access to every tool listed below — spanning african-payments, payment-gateway, mobile-money, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect Tingg Insights to Cursor via MCP
Follow these steps to wire Tingg Insights into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Tingg Insights
Why Use Cursor with the Tingg Insights MCP Server
Cursor AI Code Editor provides unique advantages when paired with Tingg Insights through the Model Context Protocol.
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 + Cursor Use Cases
Practical scenarios where Cursor combined with the Tingg Insights MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Tingg Insights in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Tingg Insights immediately.
"List the last 5 payment transactions in my Tingg account."
"Show me my account performance metrics."
"Check the status of payout 'payout_10293'."
Troubleshooting Tingg Insights MCP Server with Cursor
Common issues when connecting Tingg Insights to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Tingg Insights + Cursor FAQ
Common questions about integrating Tingg Insights MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.