Skip to main content
Glama
Sign In
a4sx-mcp

a4sx-mcp

by crossvault
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to a4sx-mcp

No user-submitted related servers found.

    Related Servers

    • pi-mcp

      ziyzhu
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients create, resume, message, and stop Pi coding-agent sessions running on another machine, with conversations that survive client disconnects and server restarts. Sessions can be kept loopback-only or published privately to trusted callers over Tailscale HTTPS.
      1
      Apache 2.0

    • agent-bus

      rishabhjava
      A
      license
      A
      quality
      D
      maintenance
      Enables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.
      5
      6 npm
      MIT

    • Context Hub

      Panwenzhuo0211
      A
      license
      A
      quality
      C
      maintenance
      Exposes bounded MCP tools that let connected coding agents resolve a matter by natural language, search and page through an archived read-only store of Codex and ZCode session history, and write back attributed notes with evidence IDs without auto-merging disagreements.
      12
      1
      MIT

    • Sub-Agents MCP Server

      sylvie16231
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to define reusable Markdown-based coding agents and run them through MCP-compatible clients using a chosen coding CLI backend, with shared model and permission settings plus optional session continuation.
      315 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool occupies a distinct stage of the session workflow: search finds IDs, get_session_summary inspects, acquire_session adds to library, fetch_session_context loads it, and publish_session stores transcripts. The descriptions explicitly clarify boundaries (e.g. acquire never buys, publish is private), leaving no realistic confusion.

    Naming Consistency5/5

    All five tools follow a consistent snake_case verb_noun pattern (search_, get_, acquire_, fetch_, publish_ + noun). Verb choices are predictable and readable with no mixed conventions.

    Tool Count5/5

    Five tools cleanly map to the discover-inspect-acquire-load-publish lifecycle of a session marketplace/library. Nothing feels redundant or missing for the stated scope.

    Completeness4/5

    The full core workflow is covered: search, inspect, acquire, load context, and publish. Minor gaps exist, such as no explicit tool to remove or manage library entries or list one's own library contents beyond scope=library search, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources