ESP32 MCP Server

Created By
navadoa year ago
Allow AI models connect to ESP32 exposed interfaces. AI generated MCP server for ESP32.
Overview

what is ESP32 MCP Server?

ESP32 MCP Server is a Model Context Protocol (MCP) implementation for ESP32 microcontrollers, allowing AI models to connect to ESP32 exposed interfaces through a WebSocket-based interface for resource discovery and monitoring.

how to use ESP32 MCP Server?

To use the ESP32 MCP Server, power on the ESP32, connect to its access point, configure your WiFi credentials via a web interface, and then connect to the MCP server using WebSocket on port 9000.

key features of ESP32 MCP Server?

  • MCP protocol implementation (v0.1.0)
  • WebSocket server for real-time updates
  • Resource discovery and monitoring
  • WiFi configuration via web interface
  • Thread-safe request handling
  • Comprehensive test suite
  • AsyncWebServer integration
  • LittleFS support for configuration storage

use cases of ESP32 MCP Server?

  1. Connecting AI models to IoT devices for real-time data processing.
  2. Monitoring and managing ESP32 resources remotely.
  3. Developing applications that require real-time communication with ESP32 microcontrollers.

FAQ from ESP32 MCP Server?

  • What hardware is required to run the ESP32 MCP Server?

You need an ESP32 S3 DevKitC-1 board and a USB cable for programming.

  • Is there a web interface for configuration?

Yes! The ESP32 MCP Server provides a web interface for WiFi configuration.

  • How can I test the server?

You can run the test suite using PlatformIO commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
navado
Star
-
Language
-
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)

a day ago