4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
MagicBell MCP Server

Bring Notifications
to VS Code Copilot

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

MCP Inspector GDPR Free for Subscribers
Create BroadcastGet BroadcastList Broadcasts

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
MagicBell

What is the MagicBell MCP Server?

Connect your MagicBell project to any AI agent to orchestrate multi-channel notification workflows. Trigger broadcasts, check delivery status, and manage communication logs through natural conversation.

What you can do

  • Broadcast Management — List all active and past broadcasts sent through your project to track communication history.
  • Detailed Inspection — Fetch specific broadcast metadata, content, and processing status using unique UUIDs.
  • Trigger Notifications — Create and send new broadcasts with custom titles, body content, and specific recipient filters.
  • Multi-channel Control — Handle channel-specific overrides for email, SMS, and push notifications to ensure the right message reaches the right place.

How it works

  1. Subscribe to this server
  2. Enter your MagicBell Project JWT
  3. Start sending and monitoring notifications from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Product Managers — trigger system-wide announcements or feature updates without touching the technical dashboard.
  • Support & Ops Teams — quickly verify if a specific broadcast was successfully processed and delivered to users.
  • Developers — test notification payloads, categories, and overrides directly from your code editor during development.

Built-in capabilities (3)

create_broadcast

Create a new broadcast

get_broadcast

Fetch a specific broadcast

list_broadcasts

List all broadcasts in the project

Why VS Code Copilot?

GitHub Copilot Agent mode brings MagicBell data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 3 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

MagicBell in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

MagicBell and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect MagicBell 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ 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
Enterprise Security

Why teams choose Vinkius for MagicBell in VS Code Copilot

The MagicBell 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 3 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.

MagicBell
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 MagicBell for VS Code Copilot

Every tool call from VS Code Copilot to the MagicBell 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 I send a notification to specific users or groups?

Yes! When using the create_broadcast tool, you can provide an array of user IDs or emails in the recipients field to target specific individuals or segments.

02

How do I check if a broadcast has been successfully processed?

You can use the get_broadcast tool with the unique broadcast ID. It will return the current processing status and metadata for that specific notification event.

03

Is it possible to customize the message content for different channels like Email or SMS?

Absolutely. The create_broadcast tool includes an overrides parameter where you can specify different content or templates for specific channels (email, sms, push).

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.

Explore More MCP Servers

View all →