NodeMCU MCP (Model Context Protocol) Service

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is NodeMCU MCP?

NodeMCU MCP is a service designed for managing NodeMCU devices using the Model Context Protocol (MCP). It provides a RESTful API and WebSocket interface for seamless integration with AI tools and IoT device management.

How to use NodeMCU MCP?

To use NodeMCU MCP, install it via npm or from source, configure your environment settings, and run the server. You can then interact with your NodeMCU devices through the provided API or WebSocket interface.

Key features of NodeMCU MCP?

  • Device management for NodeMCU devices
  • Real-time communication via WebSocket
  • Remote configuration and command execution
  • Telemetry data collection
  • Secure API access with JWT authentication
  • Integration with AI tools like Claude Desktop

Use cases of NodeMCU MCP?

  1. Monitoring and controlling IoT devices remotely.
  2. Integrating AI capabilities into IoT applications.
  3. Collecting and analyzing telemetry data from devices.

FAQ from NodeMCU MCP?

  • Can I use NodeMCU MCP with any NodeMCU device?
    Yes, NodeMCU MCP is compatible with all ESP8266/NodeMCU devices.

  • Is there a cost to use NodeMCU MCP?
    No, NodeMCU MCP is open-source and free to use.

  • How do I secure my API access?
    API access is secured using JWT authentication, which you can configure in your environment settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago