Pushbullet MCP Server for CursorGive Cursor instant access to 12 tools to Get Api Status, List Channel Subscriptions, List Connected Devices, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Pushbullet app connector for Cursor 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
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Pushbullet and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"pushbullet": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 Pushbullet MCP Server
Connect your Pushbullet account to any AI agent and take full control of your cross-device notification and file orchestration through natural conversation. Pushbullet provides a powerful platform for bridging the gap between your phone, tablet, and computer, and this integration allows you to send notes, links, and ephemeral messages directly from your chat interface.
Cursor's Agent mode turns Pushbullet into an in-editor superpower. Ask Cursor to generate code using live data from Pushbullet and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Push & Notification Orchestration — Send instant notes, links, and addresses to individual devices or your entire network programmatically.
- Device Lifecycle Management — List all associated devices and retrieve detailed metadata, including creating new device profiles directly from the AI interface.
- Contact & Subscription Control — Access and monitor your Pushbullet contacts and channel subscriptions via natural language to keep your communications synchronized.
- Ephemeral Messaging Intelligence — Send real-time ephemeral messages for clipboard syncing and SMS bridging using simple AI commands.
- Operational Monitoring — Track push history and manage system metadata to ensure your notification workflows are always optimized.
The Pushbullet MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor 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 Pushbullet tools available for Cursor
When Cursor connects to Pushbullet through Vinkius, your AI agent gets direct access to every tool listed below — spanning cross-device-sync, notifications, file-transfer, 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 connection
Get channel feeds
List your hardware
List friends
Get push history
g. a script) to receive pushes. Add a target device
Delete a device
Delete a push
Send data to devices
Follow a channel
Verify credentials
Unfollow a channel
Connect Pushbullet to Cursor via MCP
Follow these steps to wire Pushbullet into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Pushbullet
Why Use Cursor with the Pushbullet MCP Server
Cursor AI Code Editor provides unique advantages when paired with Pushbullet through the Model Context Protocol.
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
Pushbullet + Cursor Use Cases
Practical scenarios where Cursor combined with the Pushbullet MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Pushbullet in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Pushbullet immediately.
"Push this link to my phone: https://vinkius.com"
"Send a push notification to all my devices with a reminder about the team meeting at 3 PM."
"Share this URL across all my devices and send a copy to my colleague james@meridian.io."
Troubleshooting Pushbullet MCP Server with Cursor
Common issues when connecting Pushbullet to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Pushbullet + Cursor FAQ
Common questions about integrating Pushbullet MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.