Compatible with every major AI agent and IDE
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
- Subscribe to this server
- Enter your MagicBell Project JWT
- 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 a new broadcast
Fetch a specific broadcast
List all broadcasts in the project
Why Claude Desktop?
Claude Desktop is the definitive way to connect MagicBell to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 3 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
MagicBell in Claude Desktop
MagicBell and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect MagicBell to Claude Desktop 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 | 4,000+ 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 MagicBell in Claude Desktop
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 Claude Desktop 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
MagicBell for Claude Desktop
Every tool call from Claude Desktop to the MagicBell MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
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.
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).
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Pumble
10 toolsBring your AI agent into your Pumble workspace — read channel history, post messages, create channels, and manage team communication seamlessly.

Amazon DSP
7 toolsDemand-Side Platform orchestration — manage display campaigns, audiences, and creatives via AI.

SAP S/4HANA
9 toolsManage purchase orders, business partners, inventory, and financial postings on SAP S/4HANA — the intelligent ERP.

ReadMe
10 toolsEquip your AI to directly search, read, and manage developer documentation stored in your ReadMe project.
