Skip to main content
Glama
SWITCHSCIENCE

mcp-micropython-bridge

by SWITCHSCIENCE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-micropython-bridge

No user-submitted related servers found.

    Related Servers

    • serial-mcp

      alxgmpr
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets LLMs talk to serial devices: microcontrollers, routers, modems, embedded Linux, anything with a UART.
      23
      5
      MIT

    • Device MCP Server

      akshitsinha
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for seamless integration with peripheral devices connected to your computer. Control, monitor, and manage hardware devices through a unified API.
      5
      MIT

    • flipper-mcp

      yairhdz24
      A
      license
      B
      quality
      B
      maintenance
      MCP server that enables full control of a Flipper Zero device over USB, including screenshots, radio protocols, and app development without requiring a COM port.
      35
      MIT

    • Flipper Zero MCP Server

      busse
      A
      license
      Not graded
      quality
      D
      maintenance
      Modular MCP server for interacting with a Flipper Zero from MCP-capable clients (including Claude Desktop). Supports system info, BadUSB scripts, and music playback over USB or WiFi.
      31
      MIT

    • silotek-serial-mcp

      JOCOIN94
      F
      license
      A
      quality
      B
      maintenance
      A headless MCP server that enables AI tools (like Claude Code) to read and analyze serial logs from embedded boards (ESP32, STM32) for firmware debugging, with read-only tools for log retrieval and a built-in web viewer.
      6
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, with clear separation between file reads, uploads, downloads, stream reads, and directory operations. A few pairs such as eval vs exec and read_file vs download_file require reading descriptions, but boundaries are still understandable.

    Naming Consistency5/5

    All tools use the same micropython_ prefix and snake_case verb_noun style, making the set predictable and easy to scan.

    Tool Count3/5

    29 tools is heavy for this server, and several convenience operations around file reading and streaming could likely be consolidated. The breadth is justifiable for a MicroPython bridge, but the count sits at the borderline of being excessive.

    Completeness4/5

    The surface covers connection lifecycle, execution, reset/interrupt, file CRUD, directory operations, transfers, hashing/comparison, and stream reading. Minor gaps such as recursive directory deletion or on-device copy remain, but core workflows are well covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources