nomos
Related Servers
Alternatives to nomos
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceLocal-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.133MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
- AlicenseAqualityBmaintenanceAgentic DevOps control loop and MCP server featuring polyglot Tree-sitter AST blast-radius analysis, OPA Rego policy evaluation, and isolated --network=none Docker test verification[cite: 1]. Exposes tools to inspect impacted dependency closures, validate security guardrails, and run targeted test suites.32Apache 2.0
- AlicenseAqualityBmaintenanceThe IDE for agents — read by symbol, edit against a revision, validate with your own build, revert. It is a local stdio MCP server for coding agents. It reads code by symbol with tree-sitter and real language servers (Go, Java, Scala, TypeScript, Python, Rust, Ruby), edits against a known revision and returns compiler diagnostics with each edit, runs the repository's own build, test etc.121Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.40 npmMIT
- AlicenseBqualityDmaintenanceLocal MCP server providing project cognition capabilities for AI coding agents, including context packs, impact analysis, and git diff review through stdio communication.103MIT
TDQS
Scored across 7 tools
Each tool targets a clearly distinct workflow: session orientation, status, task DAG, memory recall, impact analysis, structural X-ray, and gate capabilities. The descriptions explicitly disambiguate likely overlaps with 'Do NOT use... use X instead' guidance.
All tools use a consistent nomos_ prefix and snake_case formatting. The only minor inconsistency is grammatical style: some names are nouns (handshake, status, task_dag, capabilities) while others are verb phrases (mem_recall, verify_impact).
Seven tools is well within a healthy range for an agent-oriented orchestration/inspection server. Each tool has a distinct, justified role rather than duplicating surface area.
The read-only orientation and inspection surface is solid, but lifecycle mutations are noticeably absent: no task creation/update/completion, no memory write, and no gate execution tool. Some gaps are acknowledged via CLI alternatives, but agents cannot complete those workflows through this MCP surface alone.