Bring Call Tracking
to Cursor
Learn how to connect Nimbata 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 Nimbata MCP Server?
Connect your Nimbata account to any AI agent and take full control of your call tracking orchestration and attribution through natural conversation. Nimbata provides a robust platform for managing inbound calls, and this integration allows you to retrieve call metadata, monitor marketing sources, and manage tracking phone numbers directly from your chat interface.
What you can do
- Call & Attribution Orchestration — List all managed inbound calls and retrieve detailed metadata programmatically, including duration, caller ID, and source attribution.
- Source & Channel Intelligence — Access and monitor your marketing tracking sources (Google Ads, Facebook, etc.) and create new ones directly from the AI interface.
- Number Lifecycle Management — List all active tracking phone numbers to maintain a clear overview of your communication infrastructure via natural language.
- Call Deep-Dive — Retrieve granular details for specific calls to understand context and attribution in real-time using simple AI commands.
- Operational Monitoring — Track system health and manage attribution metadata to ensure your marketing funnels are always optimized.
How it works
1. Subscribe to this server
2. Enter your Nimbata API Key from your dashboard settings
3. Start managing your call tracking from Claude, Cursor, or any MCP-compatible client
No more manual spreadsheet exporting for basic check-ins. Your AI acts as a dedicated call analyst or marketing coordinator.
Who is this for?
- Marketing Managers — quickly retrieve source summaries and monitor attribution health without switching apps.
- Sales Teams — automate the retrieval of inbound lead metadata and track call engagement via natural conversation.
- Developers — integrate real-time call tracking data and attribution intelligence directly within the chat.
Built-in capabilities (12)
Verify connectivity
Create a tracking source
Get call details
Get recording
Get call report
Get number details
Get source details
Get source report
List calls
List tracking numbers
List tracking sources
Search calls
Why Cursor?
Cursor's Agent mode turns Nimbata into an in-editor superpower. Ask Cursor to generate code using live data from Nimbata 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
Nimbata in Cursor
Nimbata and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Nimbata 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 Nimbata in Cursor
The Nimbata 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
Nimbata for Cursor
Every tool call from Cursor to the Nimbata MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details for a specific call by its ID?
Yes! Use the get_call_details tool with the Call ID. Your agent will respond with complete metadata for the record, including duration, caller city, and marketing source in seconds.
How do I find my Nimbata API Key?
Log in to your Nimbata account, navigate to Settings > API, and you will find your unique secret token there.
Does it support tracking sources?
Yes, use the list_tracking_sources tool to retrieve all your configured channels and understand where your inbound calls are coming from via the AI.
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.