Nimbata MCP for AI. Track every lead, trace every call back to its source.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Nimbata lets you track which marketing campaigns generate phone calls. It provides call attribution analytics, monitoring inbound leads via dynamic number insertion.
You can manage call tracking sources, retrieve granular metadata for specific calls, and list all active numbers directly through your AI client.
What your AI can do
Search calls
Filters and searches through call records using specific criteria like date range or source name.
Check nimbata status
Verifies the server's current connection status to ensure data is available.
Create source
Sets up a new marketing tracking source for campaign attribution.
Retrieves comprehensive lists of calls (list_calls), searches filtered results (search_calls), and pulls granular details for single calls (get_call_details).
Gets detailed reports on marketing sources (get_source_report) and lists all configured tracking channels (list_sources).
Lists active phone numbers (list_numbers), gets details for specific numbers (get_number), and checks the server connection status (check_nimbata_status).
Allows you to create new marketing tracking sources (create_source) or retrieve details on existing ones (get_source).
Ask an AI about this
Waiting for input…
Nimbata MCP Server: 12 Tools for Call Analytics
These tools let you list, search, and pull detailed reports on every aspect of your inbound call tracking infrastructure.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Nimbata on VinkiusSearch Calls
Filters and searches through call records using specific criteria like date range or source name.
Check Nimbata Status
Verifies the server's current connection status to ensure data is available.
Create Source
Sets up a new marketing tracking source for campaign attribution.
Get Call Details
Pulls comprehensive metadata—like duration and caller ID—for one specific call...
Get Call Recording
Retrieves the URL or access key for a recorded phone conversation.
Get Call Report
Generates a detailed summary report covering multiple tracked calls.
Get Number
Retrieves specific details about an active tracking phone number, including its status.
Get Source Report
Generates a performance report showing how well a configured tracking source...
Get Source
Gets detailed information for a specific marketing source or channel.
List Calls
Lists all managed inbound calls, providing basic metadata for an overview.
List Numbers
Provides a complete list of all currently active tracking phone numbers.
List Sources
Lists every marketing source configured in the system.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Nimbata, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Nimbata. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking call sources shouldn't feel like juggling six different tabs.
Right now, figuring out campaign performance means logging into Google Ads, then Facebook Ads, then opening your CRM, and finally exporting a spreadsheet to check conversion rates. It’s slow, it involves copy-pasting IDs, and the data is almost always stale.
With Nimbata MCP Server, you just talk to your agent. You tell it: 'Show me all calls from Facebook last week.' The server runs `search_calls` and presents a clean, actionable summary of attribution metrics—no spreadsheets needed.
Nimbata MCP Server: Get full call reports instantly.
Before this, generating a comprehensive report meant manually running queries on multiple dashboards and stitching the data together. It was tedious, prone to human error, and took minutes of your day just to compile.
Now, you ask for it. The agent executes `get_call_report` and delivers the structured summary immediately. What’s different is that this is real-time intelligence, not yesterday's export.
What your AI can actually do with this
Nimbata lets you manage full call tracking and attribution right through your agent. You don't wanna leave your workflow just to check leads, so we built this server for that.
Diving Into Call Records
You can list all managed inbound calls using list_calls, which gives you basic metadata on everything that came in. If you need to narrow the focus, use search_calls to filter records based on specific criteria like date ranges or a source name. For deep background on any single conversation, call get_call_details.
That tool pulls comprehensive info like how long the call lasted and who called it (the caller ID). If you need the actual chat recording, use get_call_recording to grab the URL or access key for that specific phone conversation.
Analyzing Sources and Performance
Want to know where your money's coming from? You can check which marketing sources are running by calling list_sources. To get the specifics on one channel, use get_source to pull all the detailed info about a particular source or channel. For performance tracking, you can generate reports using get_source_report, which shows exactly how well a configured source performed over time.
You'll also find that get_call_report generates a full summary report covering multiple tracked calls when you need to look at the big picture.
Managing Assets and Numbers
You gotta keep track of your gear, right? Start by checking the connection status with check_nimbata_status to make sure all the data's available. To see every number currently active, run list_numbers. If you need details on just one specific tracking phone number—its current status and everything else—call get_number.
Creating and Tracking Sources
If your marketing needs change, you can set up a new campaign tracker using create_source to establish a brand-new source for proper attribution. You can also get detailed information on any existing tracking source through get_source, making sure all the details are right before running a campaign.
019dd12d-599d-72ae-a0c3-58ac95dae044 Here's how it actually works
The bottom line is: your AI client acts as a dedicated analyst, pulling call metadata and performance reports without you opening a single dashboard tab.
First, subscribe to the Nimbata server and enter your API Key into your AI client.
Next, prompt your agent with a specific request—like 'List all calls from Google Ads last week' or 'Get details for call ID X'.
The agent executes the necessary tool (e.g., list_calls, search_calls) and returns structured data directly in the chat.
Who is this actually for?
Marketing Managers who are tired of manually cross-referencing ad spend with lead outcomes. Sales Leads who need instant context on inbound calls. Developers building internal dashboards that require reliable, real-time call data.
Uses the server to check campaign attribution health and see performance summaries from list_sources or get_source_report without switching apps.
Requests deep-dive details using get_call_details on a specific call ID to understand the source and context before following up with a lead.
Integrates call data into custom systems by running structured queries against endpoints like list_calls or search_calls.
What Changes When You Connect
See exactly where leads are coming from. Instead of guessing, use get_source_report to quantify performance by channel (e.g., Google Ads vs. Facebook).
Stop manual data exports. You can pull full reports using get_call_report directly in the chat interface—no CSV needed.
Know your comms infrastructure instantly. Use list_numbers and get_number to check availability or details for any tracking line.
Drill down fast on single calls. If you have a call ID, use get_call_details to get the source, duration, and caller ID in one command.
Manage your setup without logging into multiple dashboards. Use list_sources or create_source directly through your AI agent.
See it in action
Auditing a poor-performing campaign source
The Marketing Manager notices Facebook leads are dipping. They prompt their agent: 'What's the performance report for Facebook Campaigns?' The agent runs get_source_report, showing that while call volume is high, the conversion rate dropped 15% this month.
Investigating a mysterious inbound lead
A Sales Rep gets a hot lead but doesn't know where it came from. They ask their agent to 'Get details for call ID 9021'. The agent uses get_call_details, revealing the source was an obscure Direct Mail campaign, allowing the rep to adjust follow-up strategy.
Onboarding a new ad channel
The Developer needs to track calls from a new LinkedIn Ad campaign. They use create_source first, giving it the unique tracking ID, then they can monitor its performance using get_source_report as soon as leads start rolling in.
Quickly checking all active lines
The Ops Engineer needs to ensure no call numbers are out of service. They run list_numbers, verifying every assigned tracking number is marked 'active' before a major campaign launch.
The honest tradeoffs
Trying to find source data manually
Logging into the main Nimbata dashboard, filtering by date range, and then trying to export the resulting spreadsheet just to check a single conversion metric.
Don't open dashboards. Instead, ask your agent: 'Run get_source_report for Google Ads last month.' The data appears instantly in the chat.
Forgetting to filter specific calls
Running a general list_calls function that spits out hundreds of entries, forcing you to scroll and manually find the one call you care about.
Always use search_calls. Filter by date or source name in your prompt. This narrows the results down immediately.
Assuming a tool does everything
Asking 'What is my ROI?' and waiting for an answer, when the system only tracks calls, not final sales revenue.
The server gives attribution (call source to call metadata). To calculate ROI, you must use the get_source_report data and cross-reference it with your internal CRM metrics.
When It Fits, When It Doesn't
Use Nimbata if your core pain point is tracing a phone call back to its specific marketing source. If you need to know which ad campaign (Google, Facebook, etc.) generated the lead or tracked number, this server is essential.
Don't use it if your problem is internal: for example, if you only want to check ticket status in Zendesk, don't use Nimbata. Similarly, if you need full CRM customer profiles (purchase history, last login), that data lives elsewhere—you'll need a different integration.
However, if you have both an external marketing source and internal lead data, this server provides the crucial bridge: it links the source to the call metadata, giving your agent the initial piece of evidence needed for deeper analysis.
Questions you might have
How do I check a call's source using get_call_details? +
The get_call_details tool provides the full metadata for any specific call ID. This includes the attributed Source field, telling you exactly which campaign or channel generated the inbound call.
Can I list all available tracking numbers with list_numbers? +
Yes, list_numbers gives you a complete inventory of every active number managed by Nimbata. This is useful for audits or planning new campaigns.
What's the difference between get_source and get_source_report? +
get_source pulls static details about a channel (like its name or setup date). get_source_report, however, gives you performance metrics—call count and conversion rates over time.
Do I need to use search_calls for everything? +
No. Use search_calls when you know the criteria (like a date range or specific source). If you just want a general overview of all recent activity, list_calls is faster.
How do I verify if my Nimbata connection is active using check_nimbata_status? +
It confirms your API key is valid and the server is accessible. This tool runs a simple ping test, confirming connectivity without needing any specific data parameters.
What information does the create_source tool need to set up a new tracking source? +
It requires defining the source name, platform type (e.g., Google Ads), and associated ruleset. This function handles the backend setup for you through your natural conversation.
Does get_call_report provide different data than just calling list_calls? +
Yes, get_call_report provides summarized metrics across a specified date range. It aggregates key performance indicators (KPIs) rather than simply listing individual call records.
How do I retrieve or access the actual media files using get_call_recording? +
This tool returns a secure, temporary URL for the audio file. Your agent uses that link to download the recording data directly into your local environment for review.
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.
We've already built the connector for Nimbata. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.