A
licenseNot graded
qualityA
maintenanceLocal-first MCP server for querying multi-repo engineering documentation artifacts from a SQLite corpus.
9 npm
AGPL 3.0
tero-mcp-lite
by tzervas
Related Servers
Alternatives to tero-mcp-lite
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA local-first, LLM-agnostic MCP server that lets you ask hard questions about your documents, media, and code, and get traceable answers entirely offline.-
- AlicenseCqualityAmaintenanceLocal-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.81,003 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceLocal MCP server for indexing personal knowledge into SQLite with hybrid search, chunk-level citations, memory tools, and agent orchestration.4MIT
- AlicenseBqualityBmaintenanceA lightweight, dependency-free MCP server that answers cited queries over a Tero corpus index.json via stdio JSON-RPC 2.0, with honest refusal semantics and no silent empty results.9MIT
- AlicenseNot gradedqualityAmaintenanceA local-first MCP server that indexes Markdown/Obsidian folders and lets AI clients retrieve cited local context through MCP.MIT
TDQS
B3/5.0
Scored across 9 tools
Disambiguation5/5
Each tool serves a clearly distinct purpose: citation, graph traversal, explain, identity, various queries, refresh, and text search. There is no functional overlap that would confuse an agent.
Naming Consistency3/5
Tool names are a mix of single-word verbs (cite, explain, refresh) and multi-word patterns (query_by_id, query_by_kind). While all are readable, there is no consistent verb_noun or pattern across the set, causing moderate inconsistency.
Tool Count5/5
Nine tools is an appropriate count for a knowledge base server. Each tool covers a needed operation without being excessive or sparse.
Completeness4/5
The tool set covers querying by ID, kind, status, text search, graph traversal, citation, and explain. For a read-only documentation system, this is comprehensive. Minor gaps like aggregation are acceptable.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive