gitnexus-stable-ops

MCP搜索检索

提供方 ShunsukeHayashi

搜索检索 stdio · 本地进程 会话登录 社区 / 第三方 ClaudeVS Code

gitnexus-stable-ops is a toolkit for intelligent codebase analysis and maintenance, helping AI agents avoid breaking unknown callers, supporting multi-repository management and automated indexing.

一句话选型结论

按资料字段整理

gitnexus-stable-ops 属于搜索检索类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude、VS Code,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 7 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

搜索检索
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Local Deployment Code Analysis AI Agents Python Multi-Repository Management Automated Indexing Production Operations

支持客户端

适用场景

Local DeploymentCode AnalysisAI Agents

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在搜索检索场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、VS Code 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
gitnexus-stable-ops当前 未标注 stdio · 本地进程 本地部署 无 2026-08-14
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方ShunsukeHayashi上游标注的维护方 ShunsukeHayashi
分类搜索检索本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-08-14上游最后核验时间

详细介绍

10.2 KB
来自项目仓库与上游目录的原文,未做删改

gitnexus-stable-ops

Give AI Agents a 360° View of Your Codebase.

Stop Copilot and Claude Code from breaking callers they don't know about.
gitnexus-stable-ops is a production ops toolkit that keeps GitNexus running reliably across 25+ repositories — zero embedding loss, zero version drift, zero dirty-graph surprises.

> "designed for autonomous agent swarms"
> — @d3thshot7777, GitNexus maintainer

Powering 39+ OpenClaw Agents · 14 upstream PRs → 7 merged · 3+ months production

English · 中文 · 日本語


Quick Start```bash

git clone https://github.com/ShunsukeHayashi/gitnexus-stable-ops.git
cd gitnexus-stable-ops && make install

Diagnose a repo

bin/gitnexus-doctor.sh ~/dev/my-repo my-repo MyClassName

Smart reindex (skips if up-to-date, protects embeddings)

REPO_PATH=~/dev/my-repo bin/gitnexus-auto-reindex.sh

See what breaks if you change a class

gni impact AuthService
``````
✅ Direct callers (d=1): UserController.login, SessionManager.refresh
⚠️ Transitive deps (d=2): 14 files affected
🔴 Risk: HIGH — update callers before merging


---

## Why This Exists

GitNexus is one of the most capable open-source code intelligence engines available today. But running it in **production** — across dozens of repositories, with automated reindexing, inside AI agent workflows — exposes four critical operational problems:

| Problem | Impact | This toolkit's fix |
|---------|--------|--------------------|
| **Version drift** | CLI and MCP reference different versions, causing data corruption | Pinned binary (`$GITNEXUS_BIN`) used by all scripts |
| **Embedding loss** | `analyze --force` silently deletes embeddings | Auto-detect existing embeddings, add `--embeddings` flag automatically |
| **Dirty worktree** | Reindexing uncommitted work pollutes the code graph | Skip dirty repos by default (`ALLOW_DIRTY_REINDEX=0`) |
| **Impact instability** | `impact` crashes on arm64 macOS with concurrent queries | Graceful fallback to context-based analysis |

**We discovered and solved these problems running GitNexus on 25+ repos for 3+ months.**

---

## Production Stats

| Metric | Value |
|--------|-------|
| Repositories indexed | **25+** |
| Symbols in knowledge graph | **32,000+** |
| Edges (relationships) | **73,000+** |
| AI agents using the graph | **40** (OpenClaw MAS) |
| Embedding loss incidents | **0** since v1.0 |
| Upstream PRs merged to GitNexus | **7 of 14** submitted |
| Production uptime | **3+ months** |

---

## How AI Agents Use This```
Agent receives task: "Fix auth bug in service-api"
    |
    +-- 1. gni impact AuthService   --> What breaks if we change it?
    +-- 2. gni context AuthService  --> Get callers, callees, dependencies
    +-- 3. Agent writes code fix
    +-- 4. auto-reindex.sh          --> Graph stays current (post-commit hook)

Key insight: When AI agents share a code knowledge graph, they avoid breaking callers they don't know about. gni impact is the difference between a safe refactor and a 2 AM incident.```yaml

Example: OpenClaw 39-agent system

steps:
- agent: dev-architect
action: gni impact TargetClass --direction upstream
purpose: Blast radius before code change

  • agent: dev-coder
    action: gni context TargetClass
    purpose: Understand dependencies before writing fix

  • trigger: post-commit hook
    action: gitnexus-auto-reindex.sh
    purpose: Graph stays current for the next agent


---

## Features

| Script | Purpose |
|--------|---------|
| `bin/gni` | Production CLI wrapper — readable output, cypher stderr capture, impact fallback |
| `bin/gitnexus-doctor.sh` | Diagnose version drift, index health, MCP config, embedding status |
| `bin/gitnexus-smoke-test.sh` | End-to-end health check (analyze → status → list → context → cypher → impact) |
| `bin/gitnexus-safe-impact.sh` | Impact analysis with automatic context-based fallback on failure |
| `bin/gitnexus-auto-reindex.sh` | Smart single-repo reindex (stale detection + embedding protection + dirty skip) |
| `bin/gitnexus-reindex.sh` | Batch reindex recently changed repos (cron-friendly) |
| `bin/gitnexus-reindex-all.sh` | Reindex all registered repos with safety defaults |
| `bin/gitnexus-install-hooks.sh` | Install git hooks for auto-reindex on commit/merge |

---

## Safety Defaults

| Feature | Default | Override |
|---------|---------|----------|
| Embedding protection | Auto-detect and preserve | Always on |
| Dirty worktree skip | Skip dirty repos | `ALLOW_DIRTY_REINDEX=1` |
| Impact fallback | Context-based JSON on failure | Always on |
| Version pinning | `$GITNEXUS_BIN` | Set env var |

## Environment Variables

| Variable | Default | Purpose |
|----------|---------|---------|
| `GITNEXUS_BIN` | `~/.local/bin/gitnexus-stable` | Pinned GitNexus CLI path |
| `REGISTRY_PATH` | `~/.gitnexus/registry.json` | Indexed repo registry |
| `ALLOW_DIRTY_REINDEX` | `0` | Allow reindexing dirty worktrees |
| `REPOS_DIR` | `~/dev` | Root directory for batch reindex |
| `LOOKBACK_HOURS` | `24` | How far back to check for changes |

---

## Edge Cases & Lessons Learned

After 3 months of production use:

| Edge case | Status | Notes |
|-----------|--------|-------|
| LadybugDB concurrent query lock errors | ✅ Fixed upstream PR #425 + local fallback | Use `gitnexus-safe-impact.sh` for older versions |
| Embedding silent deletion on `--force` | ✅ Zero incidents since v1.0 | Auto-detects `meta.json`, adds `--embeddings` |
| Version drift between CLI and MCP | ✅ Pinned binary | All scripts use `$GITNEXUS_BIN` |
| Dirty worktree graph pollution | ✅ Skipped by default | Override: `ALLOW_DIRTY_REINDEX=1` |
| Large monorepo heap exhaustion | ✅ Detected and logged clearly | Set `NODE_OPTIONS=--max-old-space-size=8192` |

---

▶ Agent Context Graph (v1.3.0) — Index agents, skills, and cluster topology

Beyond code symbols, gitnexus-stable-ops indexes **agent-level entities** from your workspace — giving LLMs a live map of *who can do what and where*.

### What it indexes

| Entity | Source | Description |
|--------|--------|-------------|
| `Agent` | `KNOWLEDGE/AGENTS_*.md` frontmatter | Named agents with roles, pane IDs, society membership |
| `Skill` | `SKILL/**/*.md` | Skills with priority, keywords, script paths |
| `KnowledgeDoc` | `KNOWLEDGE/**/*.md` | Reference docs and context files |
| `MemoryDoc` | `MEMORY/**/*.md` | Session memories and daily logs |
| `ComputeNode` | `workspace.json nodes[]` | Physical/virtual machines in your cluster |
| `WorkspaceService` | `workspace.json services[]` | Deployed agents/services with model info |

### Progressive Disclosure

| Level | Tokens | Use case |
|-------|--------|----------|
| `--level 1` | ~100 | LLM system prompt overview |
| `--level 2` | ~400 | Default context injection |
| `--level 3` | ~2000 | Deep dive with full edges |
```bash
# Build the agent graph
gni agent-index ~/dev/MY_WORKSPACE --force

# Query at different detail levels
gni aq "deploy agent"   --level 1
gni aq "cc-hayashi"     --level 2
gni aq "announce skill" --level 3

# Auto-generate CLAUDE.md / AGENTS.md
gni cg . --update

For the full guide, see docs/agent-context-graph.md.


▶ Production Deployment — Docker and cron setup

Docker```dockerfile

FROM node:22-slim
RUN npm install -g gitnexus@1.4.6
RUN git clone https://github.com/ShunsukeHayashi/gitnexus-stable-ops.git /opt/stable-ops \
&& cd /opt/stable-ops && make install
RUN ln -sf $(which gitnexus) /usr/local/bin/gitnexus-stable
ENV GITNEXUS_BIN=/usr/local/bin/gitnexus-stable
ENV REPOS_DIR=/repos
COPY crontab /etc/cron.d/gitnexus
CMD ["cron", "-f"]


### Cron schedule```cron
# Smart reindex: only repos changed in last 24h
0 3 * * *  REPOS_DIR=/repos bin/gitnexus-reindex.sh >> /var/log/gitnexus-reindex.log
# Weekly full reindex (Sunday 4 AM)
0 4 * * 0  bin/gitnexus-reindex-all.sh >> /var/log/gitnexus-full-reindex.log
# Health check (daily)
30 9 * * * bin/gitnexus-doctor.sh /repos/main-app main-app >> /var/log/gitnexus-doctor.log

For the full CI/CD guide, see docs/ci-cd-integration.md.


Upstream Contributions

PR Title Status
#441 Add confidence constant for similarity threshold ✅ Merged
#451 Persist chat history across sessions ✅ Merged
#453 Add structured debug logger ✅ Merged
#454 detect_changes — classify by change type ✅ Merged
#425 Fix LadybugDB concurrent lock errors with exponential backoff ✅ Merged
#455 Align QueryResult types with LadybugDB WASM API 🔄 Review
#458 Expose per-repo resources in resources/list (fix MCP discovery) 🔄 Review
#443 Add maxIterations to prevent runaway agent loops 🔄 Review
(+6 more) Error handling, performance, CI stability 🔄 Review

Compatibility

Platform Status
macOS (Apple Silicon) ✅ Primary development platform
Linux (Ubuntu, Debian, Fedora) ✅ Tested
Docker ✅ See deployment section above
Windows ⚠️ Use WSL or Git Bash

Requires: Bash 4.0+ · Git 2.0+ · jq 1.6+ · Python 3.6+ · Node.js 20+


Documentation

  • Agent Context Graph Guide — Setup, commands, LLM injection, FAQ
  • Runbook — Step-by-step operational procedures
  • Architecture — Design principles and data flow
  • MCP Integration — MCP server configuration
  • CI/CD Integration — GitHub Actions, GitLab, impact analysis in PRs
  • Enterprise FAQ — Docker, K8s, security, SLA

Contributing

Contributions welcome! See CONTRIBUTING.md.

All contributions must include tests, follow Conventional Commits, and pass make test.


Enterprise

Running GitNexus at scale in a regulated environment? Miyabi G.K. offers architecture review, custom CI/CD integration, and priority issue resolution.

📧 shunsuke.hayashi@miyabi-ai.jp
🐦 @The_AGI_WAY


License

This toolkit: MIT — covers wrapper scripts, tooling, and documentation only.

GitNexus itself is licensed under PolyForm NonCommercial 1.0.0. This toolkit calls the GitNexus CLI but does not include or redistribute any GitNexus source code. For commercial use, verify GitNexus licensing independently.


Built by Miyabi G.K.

🐦 @The_AGI_WAY · 📧 shunsuke.hayashi@miyabi-ai.jp

Active contributor to GitNexus — 14 PRs submitted, 7 merged.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
gitnexus-stable-ops 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

gitnexus-stable-ops 怎么在 Claude、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

gitnexus-stable-ops 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

gitnexus-stable-ops 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

gitnexus-stable-ops 支持哪些客户端?

资料标注支持 Claude、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

gitnexus-stable-ops 能提供哪些能力?

资料显示能力标签包括 Local Deployment、Code Analysis、AI Agents、Python、Multi-Repository Management、Automated Indexing。具体工具清单以官方文档为准。

gitnexus-stable-ops 需要什么运行环境?

运行时为 python;属于本地进程,需要在本机装好运行环境。

gitnexus-stable-ops 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-08-14。