Bring Notifications
to Cursor
Learn how to connect MagicBell to Cursor and start using 3 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns MagicBell into an in-editor superpower. Ask Cursor to generate code using live data from MagicBell and it fetches, processes, and writes. all in a single agentic loop. 3 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
MagicBell in Cursor
MagicBell and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect MagicBell to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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).
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Square
11 toolsManage payments, customers, and inventory on Square with AI agents.
Plunk Email Marketing
8 toolsAutomate your email marketing via Plunk — send transactional emails, track events, and manage contacts.
Ambee Soil
5 toolsAccess real-time soil data via Ambee — monitor soil moisture, temperature, and properties globally for precision agriculture from any AI agent.
Persona
27 toolsManage identity verification workflows via Persona — handle inquiries, manage accounts, and inspect verifications directly from your AI agent.