Bring Call Tracking
to Mastra AI
Learn how to connect Nimbata to Mastra AI 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 Mastra AI?
Mastra's agent abstraction provides a clean separation between LLM logic and Nimbata tool infrastructure. Connect 12 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
- —
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Nimbata without touching business code
- —
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
- —
TypeScript-native: full type inference for every Nimbata tool response with IDE autocomplete and compile-time checks
- —
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
Nimbata in Mastra AI
Nimbata and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Nimbata to Mastra AI 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 Mastra AI
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 Mastra AI 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 Mastra AI
Every tool call from Mastra AI 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.
How does Mastra AI connect to MCP servers?
Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
Can Mastra agents use tools from multiple servers?
Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
Does Mastra support workflow orchestration?
Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.
createMCPClient not exported
Install: npm install @mastra/mcp