a4sx-mcp
Related Servers
Alternatives to a4sx-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets 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.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables 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.52 npmMIT
- AlicenseAqualityBmaintenanceMCP server for sharing, searching, and pulling AI coding-agent sessions (Claude Code and Codex) directly from the agent, with automatic capture and link-based sharing.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT or other MCP clients to consult explicitly configured local repositories and worktrees, search and read UTF-8 text, optionally access authorized Codex conversation history, and write new Markdown candidates only after confirmed preview.MIT
- FlicenseNot gradedqualityFmaintenanceEnables AI coding agents to persistently store and retrieve conversation history with hybrid semantic and keyword search, cross-encoder reranking, session filtering, and archiving through MCP tools.-
- AlicenseNot gradedqualityAmaintenanceBrowse, search, rename, split, and clean up Claude Code sessions via MCP, Web UI, or VSCode extension.022MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.