Desktop MCP
Connect an MCP client to EMWaver.
macOS, Windows, and Linux desktop apps can expose a local MCP server while the app is running. This lets an MCP-capable client inspect the connected board, manage local scripts, run JavaScript, and call hardware primitives through the same app-owned runtime used by the UI.
How to enable it
- Open the EMWaver desktop app.
- Click the MCP button in the app toolbar.
- Enable the local MCP server.
- Copy the endpoint and bearer token from the modal.
- Add those values to an MCP client that supports local Streamable HTTP servers.
The server is local to your machine. It binds to loopback at 127.0.0.1, requires the bearer token shown by the app, and stops when the desktop app exits.Endpoint
The default endpoint is:
http://127.0.0.1:3923/mcpSend the token as an authorization header:
Authorization: Bearer YOUR_EMWAVER_MCP_TOKENAvailable tools
| Tool | Use |
|---|---|
| list_scripts | List local scripts the desktop app can run. |
| read_script | Read a script source file. |
| write_script | Create or update a local script file. |
| run_script | Run JavaScript through the app runtime. |
| stop_script | Stop an MCP-started script run. |
| device_state | Inspect the selected board and transport state. |
| spi_transfer | Send an SPI transfer through the connected board. |
| gpio_read | Read a GPIO pin. |
| gpio_write | Write a GPIO pin. |
| analog_read | Read an analog input. |
Platform behavior
- macOS, Windows, Linux: host the MCP server inside the running desktop app.
- iOS and Android: run local scripts but do not host an MCP endpoint.
- Local core: scripts and hardware access still work without MCP enabled.