Skip to main content
Glama
mcp2everything

mcp2tcp

by mcp2everything
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp2tcp

No user-submitted related servers found.

    Related Servers

    • mcp2mqtt

      mcp2everything
      A
      license
      B
      quality
      D
      maintenance
      Links IoT devices to AI large models using the MCP and MQTT protocols, enabling natural language control, real-time AI responses, and complex instruction execution for interconnected IoT devices.
      3
      370
      MIT

    • mcp2mqtt

      swesmith-repos
      A
      license
      B
      quality
      Not graded
      maintenance
      An MCP server that bridges the physical world and AI models by enabling natural language control of IoT hardware via the MQTT protocol. It supports real-time device monitoring, command publishing, and response handling for seamless integration between AI clients and physical devices.
      3
      MIT

    • ESP32 MCP Server

      tinkeriotops
      F
      license
      Not graded
      quality
      D
      maintenance
      Bridges the Model Context Protocol (MCP) with ESP32 devices running Tasmota firmware, enabling LLMs to send structured commands like toggling relays or reading sensors via HTTP.
      1
      -

    • Jeltz

      heath0xFF
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to physical devices via MCP, enabling LLMs to reason about sensor data, perform cross-device correlation, and interpret anomalies.
      4
      Apache 2.0
    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

    C2.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: 'led' controls an LED, 'pico_info' queries board information, and 'pwm' adjusts PWM settings. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task without confusion.

    Naming Consistency3/5

    The naming is mixed in style: 'led' and 'pwm' are acronyms or abbreviations, while 'pico_info' uses snake_case. However, all names are short and readable, with no chaotic variations, but they lack a consistent verb_noun pattern or uniform casing.

    Tool Count3/5

    With only 3 tools, the set feels thin for a server named 'mcp2tcp', which might imply broader capabilities like TCP communication or device control. While each tool is distinct, the count is borderline low for the apparent scope of interacting with a Pico board.

    Completeness2/5

    The tool surface is severely incomplete for controlling a Pico board via TCP. There are no tools for basic operations like reading sensor data, sending/receiving TCP data, or managing connections. The existing tools cover only LED, PWM, and info queries, leaving significant gaps that could cause agent failures in broader tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources