Skip to main content
Glama
Mentat-Uran

sts2-ironclad-agent

by Mentat-Uran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sts2-ironclad-agent

No user-submitted related servers found.

    Related Servers

    • sts2-mcp-bridge

      brmarcosbr
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an MCP agent to observe and command Slay the Spire 2 game state via HTTP, and optionally autopilot combat with a local deterministic policy, without LLM in the critical path.
      MIT

    • STS2 AI Agent

      CharTyr
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to play Slay the Spire 2 by exposing game state and actions through an MCP server, supporting combat, rewards, and run management.
      327
      -
    • KeyAI PC Commander by KeyAIGit

      KeyAI PC Commanderofficial

      KeyAIGit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a local Windows MCP gateway to a KeyAI Agent Host, exposing DesktopCommanderMCP-compatible terminal tools and policy-controlled action review via stdio.
      MIT

    • Agentic Team MCP

      menma4ever
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous hierarchical multi-agent orchestration for MCP, with persistent SQLite state, real-time web monitoring, and support for mixing multiple CLI and direct API execution providers.
      1
      MIT

    • sagaz-mcp

      BabyKuramaDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables transparent MCP proxying with a hash-chained effect ledger, classifying agent actions by reversibility, enforcing approval gates, and dry-run previews of sessions.
      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

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clear, distinct roles across the pipeline: readiness, snapshotting, legal actions, planning, recommendation, execution, stepping, autoplay, and new-run setup. The only mild boundary ambiguity is between execute_proposal and step_once, both of which can submit a single action, but their descriptions distinguish lower-level proposal submission from routed decision execution.

    Naming Consistency3/5

    All names are readable snake_case, but they do not follow a single pattern. get_game_snapshot and get_legal_actions use get_, while plan_map_route, recommend_next_action, and execute_proposal use verb_noun, and preflight, step_once, and autoplay are one-off or compound names.

    Tool Count5/5

    Nine tools is a well-scoped size for an autonomous game agent. Each tool supports a distinct stage of the play loop without excessive redundancy or unnecessary surface area.

    Completeness4/5

    The tool set covers the full gameplay automation loop: preflight checks, state reads, legal-action discovery, path planning, decision recommendation, proposal execution, single-step control, bounded autoplay, and starting a new run. Minor gaps exist around explicit stop/pause or richer configuration control, but the existing tools handle those through local config and autoplay stopping conditions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources