Skip to main content
Glama
JustworxCloud

jwx-mcp

by JustworxCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to jwx-mcp

No user-submitted related servers found.

    Related Servers

    • Terminal Session Manager

      danieldoalto
      F
      license
      B
      quality
      B
      maintenance
      Enables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.
      15
      -

    • mcp-bridge

      ctrlpi
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to control one or more remote GPIO agents through a conversation by proxying tool calls to their REST APIs. It supports API-key authentication, LAN discovery, and both stdio and Streamable HTTP transports.
      14
      1
      MIT
    • Cartena MCP Server by cartena-tecnologia

      Cartena MCP Serverofficial

      cartena-tecnologia
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients like Claude to interact with Cartena tools via MCP, supporting remote OAuth or local stdio authentication.
      -

    • 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.
      -
    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

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing vs. fetching a single device, retrieving events, controlling IO persistently or momentarily, and managing rules. set_io and pulse_io are clearly differentiated by hold vs. transient behavior.

    Naming Consistency5/5

    All tool names use a consistent verb_noun pattern (list_, get_, set_, pulse_), with clear and predictable naming that mirrors the operation type.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a device interaction API, covering essential read and write operations without unnecessary bloat or missing core functionality.

    Completeness5/5

    The surface covers device discovery, state inspection, event history, and both persistent and momentary IO control, plus rule management. This is a thorough set for the apparent domain of device control and monitoring.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources