Model Context Protocol (MCP) service for NodeMCU management
Nodemcu MCP server exists for a simple reason — assistants are far more useful when they can act on Nodemcu directly instead of describing what you should do. Model Context Protocol (MCP) service for NodeMCU management.
A Model Context Protocol (MCP) service for managing NodeMCU devices. This service provides both a standard RESTful API/WebSocket interface and implements the Model Context Protocol for integration with AI tools like Claude Desktop.
NodeMCU MCP provides a management solution for ESP8266/NodeMCU IoT devices with these key capabilities: - Monitor device status and telemetry - Send commands to devices remotely - Update device configurations - Integration with AI assistants through MCP protocol
Once Nodemcu is connected, these are the calls the assistant has available:
list-devices — List all registered NodeMCU devices and their statusget-device — Get detailed information about a specific NodeMCU devicesend-command — Send a command to a NodeMCU deviceupdate-config — Update the configuration of a NodeMCU devicePrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — 1. Create a .env file based on the example: cp .env.example .envAuthentication — Response: json { "message": "Login successful", "token": "your.jwt.token", "user": { "id": 1, "username": "admin", "role": "admin" } }Contributing — Contributions are welcome! Please feel free to submit a Pull RequestThe server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Nodemcu's toolset — list-devices, get-device, send-command and 6 more — is a fair guide to whether it matches your workflow. It is maintained by amanasmuei; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Nodemcu's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list-devices | List all registered NodeMCU devices and their status |
| get-device | Get detailed information about a specific NodeMCU device |
| send-command | Send a command to a NodeMCU device |
| update-config | Update the configuration of a NodeMCU device |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | 1. Create a .env file based on the example: cp .env.example .env |
| Authentication | Response: json { "message": "Login successful", "token": "your.jwt.token", "user": { "id": 1, "username": "admin", "role": "admin" } } |
| Contributing | Contributions are welcome! Please feel free to submit a Pull Request. |
{
"mcpServers": {
"nodemcu": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/YOUR/PROJECT/mcp_server_sdk.js"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.