arale-code
OfficialRelated Servers
Alternatives to arale-code
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables compatible agents to call registered local tools and read resources through one stdio server, including harness preparation, knowledge search and document management, memory retention/recall, correction proposals, advisory decisions, tool/skill discovery, and log/source inspection.2Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents to consult a project's Git-versioned Markdown knowledge base over local stdio — checking knowledge health, listing the catalog, searching topics, and reading guides before acting. Access stays read-only, so project guidance, decisions, and lessons learned remain shared with human teammates and traceable beside the code.41MIT
- AlicenseNot gradedqualityDmaintenanceProvides a stdio MCP bridge for coding agents to query and record engineering knowledge locally, preserving debugging history, failed attempts, and verified solutions.1 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to read, navigate, and query long-term memory stored as readable, reviewable source files, exposing paged catalogs, indexed searches that explain their misses, bounded relation traces, link diagnostics, raw file access, and preflight checks of drafts against MUST constraints. It serves this read-only by default over stdio so any MCP client can start from a memory catalog and keep reading toward the answer instead of relying on a single similarity guess.1MIT

Zof MCP serverofficial
AlicenseNot gradedqualityAmaintenanceGives a compatible coding agent read-only access to bounded local verification of changes inside a single host-chosen workspace, exposing six stdio tools that inspect capabilities, static checks, impact analysis, policy evaluation, evidence generation, and suggested tests without shell access, plugin loading, or repository upload.0Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables coding agents to search local repositories and retrieve bounded, cited source chunks, look up full indexed chunks, and inspect index statistics through read-only MCP tools over stdio.MIT
TDQS
Scored across 2 tools
The two tools are mostly distinct: one lists procedures/control-guide entries and the other lists engineering-instruction IDs. They share a very similar list-by-ID/URI pattern, but the descriptions make the resource type clear enough to avoid most confusion.
Both tools follow the same predictable list_noun convention. There are no naming inconsistencies across the set.
Two tools is thin for a server surface, and both only list identifiers rather than offering broader procedure/instruction interaction. The count is borderline rather than clearly wrong, but it feels under-scoped.
The surface only lists procedure and instruction IDs/URIs; there are no tools to actually read, fetch, or operate on a procedure or instruction. Descriptions imply later reading/requesting, but the tool set does not provide those operations, creating a significant dead end.