How to Use the myDevices MCP in Cursor

Q: How do I add the myDevices server to Cursor?

Create a .cursor/mcp.json file in your project root and add the myDevices MCP Server configuration. Once saved, enable Agent mode in the chat panel to let the editor invoke tools like listdevices.

Q: How do I test myDevices commands inside Cursor?

Ask the chat to trigger a physical action by calling sendcommand. Cursor will execute the tool through the MCP protocol, allowing you to watch your hardware react while you inspect the resulting log output in your editor terminal.

Q: Can I manage multiple Cayenne applications?

Yes, the listapplications tool lets you view all registered IoT networks under your account. You can switch target applications directly in your coding session to manage different fleets of hardware.

Write IoT automation scripts in Cursor using live hardware data from the myDevices MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect myDevices MCP to Cursor

Create your Vinkius account to connect myDevices to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup myDevices with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate code with the myDevices MCP Server

The myDevices MCP Server gives Cursor Agent mode direct access to `list_devices` and `list_sensors` to inspect your hardware layout. This means your editor generates code based on your actual IoT architecture instead of placeholder variables. By calling `get_device`, Cursor reads the active configuration of your physical hardware. You can write precise data-logging scripts because the editor knows the exact JSON structure your hardware returns.

Debug sensor integration inside Cursor Agent

Pull live hardware values into your editor workspace using `get_sensor_data` to verify your parsing logic. You don't have to guess if your math is right when converting raw telemetry; Cursor pulls the live feed and tests the code against actual values. If your script handles historical aggregation, use `get_sensor_history` to feed real telemetry logs directly into your local test suite. This lets you debug edge cases with actual historical data instead of mocked arrays.

Test remote hardware control from the editor

Send live instructions to physical hardware using the `send_command` tool directly from Cursor's chat. You can test your system's response to commands without leaving your code files or opening external terminal utilities. To build automated self-healing loops, query `list_alerts` to check for active threshold breaches. Cursor can help you write scripts that automatically trigger a command when specific hardware alerts are logged.

Setup guide

Set up myDevices MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the myDevices MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent myDevices transactions." If the MCP tools are loaded correctly, Cursor will call the myDevices tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "mydevices-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by myDevices. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect myDevices now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about myDevices MCP in Cursor

Create a `.cursor/mcp.json` file in your project root and add the myDevices MCP Server configuration. Once saved, enable Agent mode in the chat panel to let the editor invoke tools like `list_devices`.

Yes, when you ask Cursor to write a script for a specific device, the Agent can run `list_sensors` or `get_sensor_data` to find the exact channel IDs it needs to write the code.

Ask the chat to trigger a physical action by calling `send_command`. Cursor will execute the tool through the MCP protocol, allowing you to watch your hardware react while you inspect the resulting log output in your editor terminal.

Yes, the `list_applications` tool lets you view all registered IoT networks under your account. You can switch target applications directly in your coding session to manage different fleets of hardware.

Your Cayenne credentials stay inside your local configuration files or Vinkius environment variables. They are never transmitted to Cursor's indexing servers, keeping your IoT sensor telemetry and device keys secure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript