nomos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only local Nomos MCP server. Use nomos_handshake, nomos_xray, nomos_verify_impact, nomos_capabilities, and nomos_mem_recall to inspect repository governance without mutating files.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nomos_handshakeA | Synthesize read-only Just-In-Time (JIT) session orientation, active task phase, and Next Actions for a repository without modifying files or Git hooks. Use when starting an agent turn to discover the active worktree and allowed phase actions. Do NOT use when checking global daemon/DB health without JIT directives (use nomos_status instead) or listing backlog tasks (use nomos_task_dag instead). |
| nomos_statusA | Return a concise snapshot of workspace lifecycle phase, active Git branch, SQLite ledger health, and aggregate task counts. Use when checking overall host/database readiness or current branch state. Do NOT use when requesting full JIT phase playbooks (use nomos_handshake instead) or scanning code debt (use nomos_xray instead). |
| nomos_task_dagA | Query unblocked causal DAG wavefront tasks (including Agent-to-Agent scope_paths, TC-* obligations, and active worktree MTPO overlap flags) ready for execution without mutating task ledger state. Use when selecting the next unblocked INT-* or SUB-* task to start (to submit a new multi-node DAG subgraph, invoke CLI 'nomos task batch -F - --json'). Do NOT use when recalling past architectural decisions or lessons (use nomos_mem_recall instead). |
| nomos_mem_recallA | Search Nomos Mneme institutional memory records (decisions, patterns, pitfalls, axioms) matching a keyword or semantic query. Use when retrieving prior architectural rationale, learned pitfalls, or workspace conventions before editing code. Do NOT use when inspecting compiled quality gate rules (use nomos_capabilities instead) or listing open backlog tasks (use nomos_task_dag instead). |
| nomos_verify_impactA | Compute the deterministic 1-hop AST reverse-dependency blast radius of packages impacted by uncommitted or branch-modified files. Use when assessing which downstream packages and test suites are affected by current edits. Do NOT use when auditing full-repository structural complexity or AI Hangover Score (use nomos_xray instead). |
| nomos_xrayA | Run a zero-write polyglot static AST structural X-Ray across a local repository directory to measure AI Hangover Score, cyclomatic/cognitive debt, and top hotspot files. Use when auditing overall codebase health, complexity hotspots, or brownfield baseline posture. Do NOT use when computing only the diff-scoped blast radius of modified files (use nomos_verify_impact instead) or looking up a single gate definition (use nomos_capabilities instead). |
| nomos_capabilitiesA | Inspect compiled Nomos Definition of Done quality gates, ambient Git/session hooks, embedded phase directives, or remediation guidance for a specific gate ID. Use when looking up gate invariants, hook behavior, or how to fix a specific gate ID. Do NOT use when searching project-specific historical decisions in Mneme (use nomos_mem_recall instead) or scanning live source files (use nomos_xray instead). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| xray-audit | Audit repository structural health via nomos_xray and summarize the AI Hangover Score and top hotspots. |
| verify-impact | Inspect reverse-dependency blast radius for modified files via nomos_verify_impact. |
| recall-pitfalls | Query verified episodic trap-to-fix lessons via nomos_mem_recall before editing. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| nomos-workspace-status | Current governance phase, active branch, database health, and unblocked task wavefront. |
| nomos-capabilities-catalog | Authoritative JSON catalog of active quality gates, ambient hooks, engines, and directives. |
| nomos-jit-directives | List of embedded and workspace Just-In-Time (JIT) phase steering playbooks. |
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.