Halfway through writing firmware for a soil moisture sensor, you realize you need a new datastream. So you stop coding, switch to the browser, open the Blynk console, navigate to the template, add the datastream, configure its data type and range, then switch back to your IDE and try to remember what you were doing.
That context switch is small on its own. But across a day of prototyping, it adds up. Every time you need to check a live reading, create a test device, or tweak an alert threshold, you leave your development environment and come back to it slightly colder.
The Blynk MCP server removes that friction. Your IDE connects directly to your Blynk account, so platform management happens in the same place you write code.
Once connected, your IDE's AI assistant has direct access to your Blynk account. Platform management becomes a conversation:
That first example — creating a template with three configured datastreams — is one sentence. The MCP server handles the data types, ranges, and configuration behind the scenes.
Prototyping. When you're iterating on firmware and hardware together, the template changes constantly. New sensor, new datastream. Renamed field, adjusted range. Doing this in the console means breaking flow every few minutes. With MCP, template changes happen inline — you describe what you need, the platform updates, and you keep writing firmware.
Debugging. Instead of opening the console to check if your device is sending the right values, query it from your editor. "What's the last reading from device X?" gives you the answer without a tab switch. When something looks wrong, you're already in the code that's causing it.
Fleet management. For teams managing deployed devices, MCP turns your editor into a lightweight operations tool. Query device status across your deployment, check which devices are offline, read aggregate sensor data. Useful during development, but also during support calls when you need to check a customer's device quickly.
The MCP server exposes the same capabilities you'd use in the Blynk web console — templates, datastreams, devices, events, automations — through natural language in your editor.
The Blynk MCP server is a remote HTTP server. You don't install anything. Point your IDE at a URL, sign in with your Blynk account, and you're connected.
It works with Claude Code, VS Code with GitHub Copilot, Cursor, Windsurf, and Claude Desktop. Setup is slightly different for each, but the pattern is the same: add a server URL, authenticate, start using it.
The fastest path. One command:
This adds Blynk to your current project. Use `--scope user` to make it available across all projects.
Or add it to `.mcp.json` in your project root:
On first use, Claude Code opens a browser window for you to sign in with your Blynk account.
Requires VS Code 1.99+ with the GitHub Copilot extension. MCP support is built into Copilot's agent mode.
Command palette: Cmd+Shift+P > "MCP: Add Server..." > select "HTTP" > enter URL `https://blynk.cloud/mcp` > server ID `blynk-mcp`.
Or create `.vscode/mcp.json` in your project root:
Note: VS Code uses `"servers"` as the top-level key, not `"mcpServers"`.
Open Settings (Cmd+Shift+P) > Tools & MCP > New MCP Server. This opens your `mcp.json` file. Add inside the `"mcpServers"` object:
Save the file. The server appears in your MCP servers list. The config lives at `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (project-level).
Edit `~/.codeium/windsurf/mcp_config.json`:
Windsurf uses `"serverUrl"` instead of `"url"`. Make sure MCP is enabled in Windsurf settings: Settings > Cascade > Model Context Protocol.
No config files needed. Open Settings > Connectors > Add Custom Connector. Name it "Blynk", enter the server URL `https://blynk.cloud/mcp`, and authenticate when prompted.
Server not found or no tools available:
Authentication fails:
Tools appear but aren't working:
If you already have a Blynk account, setup takes a minute. If you don't, start for free and connect your first device through your IDE instead of the console. The MCP server works on every Blynk plan, including the free tier.
Blynk is a low-code IoT platform used by 5,000+ businesses to build, deploy, and manage connected products. Start building →
.png)
