NEXUS
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUS_LOG_LEVEL | No | One of: debug, info, warn, error, silent | info |
| NEXUS_WORKSPACE | No | Workspace root (the jail boundary) | process.cwd() |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nexus_workspace_overviewA | Project at a glance: languages, LOC, git state, index health, entry points. |
| nexus_searchA | Search files by content (regex/literal) or by glob pattern. Gitignore-aware. |
| nexus_read_spanA | Read a line range of a file. Encoding-safe, binary-aware, injection-scanned. |
| nexus_index_buildA | Build or refresh the code index (symbols, imports, calls). Required before code-intel tools. |
| nexus_file_symbolsB | Get the symbol outline of a file (functions, classes, types, etc.). |
| nexus_find_symbolsA | Fuzzy search for symbols across the entire workspace. |
| nexus_referencesA | Find all reference sites of a symbol (calls, imports, type annotations). |
| nexus_call_graphA | Callers or callees of a function, depth-N. |
| nexus_dependency_graphA | Import dependencies of a file (what it depends on) or dependents (what depends on it). |
| nexus_repo_mapA | Ranked repo map within a token budget. Shows top symbols per file, PageRank-ordered. Most important context feature. |
| nexus_context_packB | Task-focused context bundle: repo map slice + symbol outlines of focus files + related files. |
| nexus_impact_analysisA | Blast radius of editing a symbol or file: what else would be affected? Uses reverse reachability on the dependency/call graph. |
| nexus_git_diffA | Smart git diff: stat summary + paginated hunks. Binary files flagged. |
| nexus_snapshotB | Checkpoint files before editing. Creates a restore point with full file contents. |
| nexus_restoreA | Restore files from a snapshot. Overwrites current content. DESTRUCTIVE. |
| nexus_execB | Run a command with timeout, ring-buffer output, and secret redaction. Process-group killed on timeout. |
| nexus_exec_pollB | Poll, list, or kill background exec jobs. |
| nexus_test_runA | Detect framework (jest/vitest/pytest/cargo/go) and run tests. Returns structured pass/fail counts and failures. |
| nexus_diagnoseA | Run typecheck (tsc) and linter (eslint). Parses output into structured diagnostics {file, line, col, severity, rule, message}. |
| nexus_memory_writeA | Store a persistent memory: knowledge, decision, gotcha, or preference. Survives across sessions. |
| nexus_memory_searchA | Recall memories by text query, tags, or namespace. |
| nexus_memory_forgetA | Delete memories by ID or text match. Audit-logged. DESTRUCTIVE. |
| nexus_task_submitA | Submit a task DAG (directed acyclic graph). Validates cycles. Persists across restarts. |
| nexus_task_updateA | Update task status (completed/failed/in_progress). Unblocks dependents. |
| nexus_task_statusA | View task DAG: ready, blocked, in_progress, completed, failed. |
| nexus_fanoutA | Parallel map: run a command over multiple items with concurrency limit. |
| nexus_secret_scanA | Scan files for secrets (AWS, GitHub, OpenAI, JWT, private keys, etc.). Findings are redacted. |
| nexus_audit_manifestA | Dependency inventory with risk heuristics: typosquatting, unpinned versions, abandoned packages. |
| nexus_rename_symbolB | Preview workspace-wide rename of a symbol (graph-scoped, not blind sed). Returns the changes to make. |
| nexus_server_statusA | Server self-diagnostics: index age, backend, caps, state dirs, version. |
| nexus_guideA | On-demand playbook: recommended workflows, recipes, and gotchas for using NEXUS effectively. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Most tools have clearly distinct purposes, but the number of code-analysis tools (call_graph vs dependency_graph, repo_map vs context_pack) creates some risk of mis-selection without careful reading. The memory and task tools are cleanly separated by prefix and domain.
All names share the 'nexus_' prefix and snake_case, which helps, but the internal structure is inconsistent: some use verb_noun (find_symbols, read_span), others noun_verb (memory_write, task_submit), and a few are single verbs (exec, restore, diagnose). This mixed pattern makes it less predictable than an ideal verb_noun convention.
At 31 tools, the surface is very large and spans multiple domains (code intelligence, execution, memory, tasks, security), which feels heavy for an agent to navigate efficiently. Even though each tool has a unique role, the sheer number exceeds the typical well-scoped server count.
The server covers a comprehensive range of code analysis, search, execution, testing, memory, and task management workflows. The most notable gap is the lack of a direct file-edit or apply-patch tool—rename only previews changes and exec must be used as a workaround—but this is a minor gap rather than a fatal omission.