3,400+ MCP servers ready to use
Vinkius

Nimbata MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Check Nimbata Status, Create Source, Get Call Details, and more

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Nimbata app connector for VS Code Copilot is a standout in the Industry Titans 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

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Nimbata and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "nimbata": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
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

About 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.

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.

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.

The Nimbata MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot 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 Nimbata tools available for VS Code Copilot

When VS Code Copilot connects to Nimbata through Vinkius, your AI agent gets direct access to every tool listed below — spanning call-tracking, marketing-attribution, lead-generation, 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.

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

Connect Nimbata to VS Code Copilot via MCP

Follow these steps to wire Nimbata into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Nimbata

Ask Copilot: "Using Nimbata, help me...". 12 tools available

Why Use VS Code Copilot with the Nimbata MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Nimbata through the Model Context Protocol.

01

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

02

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

03

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

04

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

Nimbata + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Nimbata MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Nimbata in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Nimbata immediately.

01

"List all tracked calls in Nimbata from today."

02

"Show me the call tracking sources I have configured and their performance."

03

"Get the recording and full details for call ID call_7823."

Troubleshooting Nimbata MCP Server with VS Code Copilot

Common issues when connecting Nimbata to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

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

Nimbata + VS Code Copilot FAQ

Common questions about integrating Nimbata MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.