LiuHe
Related Servers
Alternatives to LiuHe
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal code search for AI agents over a tree-sitter index of your repo: exact symbol lookup, scope-aware usages, call graph and impact analysis, AST pattern search, indexed grep and semantic search. 28 MCP tools, 19 languages, runs fully offline.2812MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to perform deterministic, model-free repository analysis and patch operations—tree-sitter repo maps, symbol/reference lookup, and SEARCH/REPLACE parsing/validation—via a CLI or MCP stdio server, without ever calling a language model.1MIT
- AlicenseNot gradedqualityAmaintenanceStandalone MCP server for code structure analysis using tree-sitter. Directory trees, symbol definitions, and call graphs without reading raw source files. Supports Rust, Python, Go, Java, TypeScript, Fortran, JavaScript, C/C++, and C#. Benchmarked up to 68% fewer tokens vs native tools.7Apache 2.0

mcp-reposkeinofficial
AlicenseAqualityAmaintenanceDeterministic code-graph (GraphRAG) over your repo for LLM agents — local-first, git-native, zero-infra, served via MCP. Python, TS/JS, Rust, Go, Java, C#.813Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query code structure efficiently through 16 MCP tools, including symbol lookup, full-text search, dependency analysis, and refactor planning, powered by tree-sitter parsing and index-backed code intelligence.3MIT
- AlicenseAqualityAmaintenanceSee your codebase the way an agent sees it: codetopo turns any source repository into a deterministic, queryable code graph of symbols, calls, and references. It runs locally as an MCP server (12 tools), CLI, and HTTP API, written in Rust.201AGPL 3.0
TDQS
Scored across 13 tools
The editing surface is crowded: code_patch, code_batch, edit_transaction, and code_worktree all mutate files, and the boundary between code_batch's atomic multi-file apply and edit_transaction's multi-file rollback/undo is not sharp. code_read and code_query also overlap on reading file contents, though descriptions provide some guidance.
All tools use snake_case and ten of thirteen share a code_ prefix; edit_transaction and invoke_capability are exceptions but remain readable. The mix of verb and noun suffixes (code_read vs code_task/code_worktree) is a minor inconsistency.
13 tools is within the well-scoped 3–15 range for a code-editing workflow. Each tool maps to a planning, reading, editing, verification, maintenance, or lifecycle concern.
The surface covers planning, querying, reading, single/multi-file edits, transactions, worktrees, checks, audits, maintenance, and task control. Minor gaps remain around explicit file deletion/rename and first-class diff/undo of applied patches.