Skip to main content
Glama

Related Servers

Alternatives to mcp-bridge

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • 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.
      -
    • 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to discover and call local MCP tools over a Streamable HTTP endpoint using Groq for reasoning and tool selection.
      -

    TDQS

    A3.8/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a distinct domain and action: GPIO read/write/scan/config/watched, sensor config/read, config load/read/write, agent lifecycle, and agent listing. Overlaps such as GPIO read-all versus scan are differentiated by scan returning pin metadata while read returns values, so selection is clear.

    Naming Consistency4/5

    All tools use the mcp_ prefix and snake_case with a domain_action pattern, which is highly predictable. Minor deviations include mcp_agents_list (plural domain) versus mcp_agent_* (singular) and mcp_gpio_watched using an adjective rather than a verb.

    Tool Count5/5

    With 14 tools, the set is well-scoped for bridging to hardware agents, covering GPIO, sensors, configuration, and agent lifecycle without obvious redundancy. Each tool earns its place and the count stays within a manageable range.

    Completeness4/5

    The surface covers most core operations: GPIO read/write/config/scan, sensor config/read, config load/read/write, agent list/restart/upgrade/logs. Minor gaps remain, such as no explicit sensor listing tool or dedicated agent start/stop operations, but they are largely workaroundable via existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues