Skip to main content
Glama
ctrlpi

mcp-bridge

by ctrlpi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-bridge

No user-submitted related servers found.

    Related Servers

    • jwx-mcp

      JustworxCloud
      F
      license
      A
      quality
      C
      maintenance
      Exposes Justworx devices to AI agents as MCP tools and resources, backed by the public Developer API. Supports local stdio and hosted remote OAuth operation for controlling device IO, rules, and viewing live state.
      6
      -

    • idh

      taisuii
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover and interact with iOS apps through a local MCP gateway, converting remote Streamable HTTP MCP endpoints into stdio tools. Provides dynamic device discovery, tool schema introspection, and deterministic tool calling for app analysis.
      -

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • Triclops

      morepriyam
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 238 schema-typed tools over streamable-HTTP MCP that let a client drive a Flipper Zero, an AWOK Biscuit (ESP32-C5) and an ESP32 Marauder — scanning, screen mirroring, storage, and other device operations — from natural-language or direct tool calls. Transmit/attack tools stay behind an explicit human confirmation gate.
      MIT
    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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    The surface splits cleanly by resource: GPIO (read/write/config/scan/watched), config (read/write/load), sensors (config/read), and agent lifecycle (list/restart/upgrade/logs). The only real overlaps are config_write vs config_load (partial dict update vs full-document load) and gpio_read with 'all' vs gpio_scan, but the descriptions make the intended distinctions (nested grouping, backup-then-load, pin metadata vs raw values).

    Naming Consistency4/5

    All tools share a predictable prefix + domain_action shape (mcp_gpio_read, mcp_config_write, mcp_sensor_read, mcp_agent_restart). Minor deviations: mcp_agents_list uses the plural 'agents' where the lifecycle tools use 'agent', and mcp_gpio_watched is an adjective rather than a verb (a list operation). Overall still readable and largely uniform.

    Tool Count5/5

    14 tools spread across four coherent domains (GPIO, sensors, config, agent lifecycle) with no filler entries. Each tool covers a distinct operation needed by a device bridge, well within the 3-15 sweet spot.

    Completeness4/5

    GPIO has full lifecycle coverage (scan, read, write, configure, watched-list) and config supports read/write/load including a reset path; sensors support configure/read plus removal via remove=true. Gaps are minor: no explicit agent add/remove/rename (relying on the hourly LAN sweep) and no dedicated sensor list beyond the config read's sensors group.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources