Skip to main content
Glama
n1snt

redux-mcp

by n1snt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to redux-mcp

No user-submitted related servers found.

    Related Servers

    • state-bridge-mcp

      jonjoe
      F
      license
      A
      quality
      D
      maintenance
      Bridges Zustand stores over WebSocket, enabling MCP-capable AI to inspect and manipulate live application state.
      5
      -

    • Tesseron

      Eigenwise
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI agents to execute typed live-app actions over WebSocket, allowing agents to directly interact with real application state without browser automation or scraping.
      20
      -

    • rosbridge-mcp

      hieutachi
      A
      license
      A
      quality
      A
      maintenance
      Connects AI agents to ROS 2 robots via rosbridge, enabling observation, inspection, and control of robot topics, services, and actions through natural language.
      11
      2
      MIT

    • Godot MCP Bridge

      farrasfadhils
      F
      license
      C
      quality
      F
      maintenance
      Enables AI assistants to control Godot game engine projects through a WebSocket bridge. Supports scene editing, node manipulation, script management, and project introspection via 163 registered tools.
      100
      1
      -

    • reactotron-mcp

      steve228uk
      A
      license
      Not graded
      quality
      F
      maintenance
      Acts as a proxy between your app and Reactotron, enabling AI assistants to read logs, inspect state, monitor network requests, and trigger custom commands.
      21 npm
      3
      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.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a unique purpose: dispatching actions, retrieving actions/history, getting state, computing state diffs, and resetting state. No overlaps exist.

    Naming Consistency5/5

    All tools follow the consistent pattern 'redux_verb_noun', using snake_case and clear verbs (dispatch, get, reset). No deviations.

    Tool Count5/5

    Five tools cover the essential operations for Redux state management without being excessive or insufficient. The count matches the domain scope.

    Completeness5/5

    The set covers all key Redux interactions: dispatching, reading state, diffing, resetting, and viewing action history. No obvious gaps for a basic server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources