Txa_MCP
Related Servers
Alternatives to Txa_MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides AI coding agents with structured, evidence-based diagnostics about the local development environment, detecting tech stack, runtime mismatches, dependency state, services, ports, and Git status without exposing secrets or using network calls.10Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables LLM clients to inspect local dev environments—Docker container health, pnpm workspace integrity, and stuck process detection—without manual terminal copy-pasting.MIT
- AlicenseAqualityBmaintenanceNext-gen AST codebase map, token compression (70%~85% savings), and context packaging engine for AI coding agents & IDEs.33MIT
- AlicenseAqualityBmaintenanceVS Code Extension & Model Context Protocol Suite Orchestrator for Cursor, Claude Desktop, and VS Code IDEs.124MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI-driven development tools including file system operations, multi-language code analysis with tree-sitter, Git operations, code execution, and system information retrieval.MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI clients with safe, structured access to local filesystem, Git repositories, and project contexts, featuring file operations, git status/diff, project management, and built-in code review/bug analysis prompts.681 npmMIT
TDQS
Scored across 36 tools
Multiple tools have overlapping purposes, such as edit_code, replace_in_file, quick_search_replace, and write_file all modifying files. Local and cloud variants of memory and todo management further blur boundaries, making it hard to select the correct tool.
Most names follow a verb_noun pattern, but the verbs are inconsistent (list, get, read, search) and some names like github_cloud or quick_search_replace break the pattern. Mixing of local/cloud prefixes (memory_save vs cloud_memory_save) adds to the inconsistency.
With 36 tools, the set is overly large for its apparent scope. Many tools could be consolidated (three replace tools, two todo managers, two memory stores), and the high count makes the server feel bloated rather than comprehensive.
The tool set covers a broad range of development tasks (file ops, git, system info, dependencies, cloud), but gaps exist such as no direct local git commit/push (only via cloud) and no file copy/move. The run_shell tool can compensate for some missing operations, but the redundancy reduces overall completeness.