3,400+ MCP servers ready to use
Vinkius

Bring Call Tracking
to VS Code Copilot

Learn how to connect Nimbata to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Check Nimbata StatusCreate SourceGet Call DetailsGet Call RecordingGet Call ReportGet NumberGet SourceGet Source ReportList CallsList NumbersList SourcesSearch Calls
Use with Your AI Agent
Ask AI about this MCP Server
ChatGPT Claude Perplexity

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)

check_nimbata_status

Verify connectivity

create_source

Create a tracking source

get_call_details

Get call details

get_call_recording

Get recording

get_call_report

Get call report

get_number

Get number details

get_source

Get source details

get_source_report

Get source report

list_calls

List calls

list_numbers

List tracking numbers

list_sources

List tracking sources

search_calls

Search calls

Why VS Code Copilot?

GitHub Copilot Agent mode brings Nimbata data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • —

    VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • —

    Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • —

    Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • —

    GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Nimbata in VS Code Copilot

AI Agent→Vinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Nimbata and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Nimbata to VS Code Copilot 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.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Use with Your AI Agent View step-by-step setup guide for VS Code Copilot →
Enterprise Security

Why teams choose Vinkius for Nimbata in VS Code Copilot

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 VS Code Copilot 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.

Use with Your AI Agent View full Nimbata details →
Nimbata
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Nimbata for VS Code Copilot

Every tool call from VS Code Copilot to the Nimbata MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.