AI Workspace Kit
Related Servers
Alternatives to AI Workspace Kit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with shared project memory, compact evidence-first context, status checks, durable handoffs, and encrypted cross-device checkpoints through MCP.1AGPL 3.0
- FlicenseAqualityBmaintenanceA read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.16-
- AlicenseNot gradedqualityCmaintenanceA local MCP bridge that gives ChatGPT bounded read and search access to exactly one approved repository, with fixed handoff writers for task delegation to a separate coding agent.56 npm25MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT Pro web to securely read workspace files, git diffs, and test records through OAuth-protected read-only MCP tools, so it can plan and review while Codex handles execution without uploading the repository.MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first Knowledge Management System that exposes markdown-based durable memory as MCP tools for Codex and ChatGPT, enabling search, read, write, and promotion workflows with project and global scopes.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: memory recall, checkpoint persistence, local document search, artifact reading, and health checking. The descriptions explicitly separate session memory (workspace_recall) from local document search (search_local) and clarify that read_local_artifact must follow search_local. This leaves little chance of misselection.
All names use snake_case, but the set mixes two prefix families (workspace_ and local/search/read) and inconsistent verb/noun structures such as workspace_recall, workspace_checkpoint, workspace_health, search_local, and read_local_artifact. The names remain readable, but the pattern is not fully predictable.
Five tools is well-scoped for a workspace memory and local-document kit. Each tool covers a distinct operation and none feels redundant or gratuitous. This is squarely within the ideal 3–15 range.
The surface covers core retrieval, persistence, local search/read, and health checking, which are the main workflows for this domain. Minor gaps remain around memory lifecycle operations such as updating, deleting, or listing checkpoints, but agents can likely work around these limitations.