Does the claude-context MCP server auto-sync code indexes after initial indexing?

6 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Auto-sync / incremental index updates are not available as a user-facing feature yet — a maintainer confirmed it is a separate feature request being tracked. The separate stuck-reindex bug is fixed in v0.1.5 (PR #282): force=true now clears stale indexing state, and interrupted indexing is automatically reset when the MCP server restarts. If you hit "already being indexed" or a permanently stuck index, update to v0.1.5.

  What currently exists (confirmed by a user who inspected v0.1.14): the MCP server exposes only index_codebase, search_code, clear_index, and get_indexing_status — there is no public incremental-sync tool. Internally, incremental refresh does exist (SyncManager.handleSyncIndex() calls Context.reindexByChange(...)), but it is not reachable from an MCP client. With CLAUDE_CONTEXT_BACKGROUND_SYNC=false and CLAUDE_CONTEXT_TRIGGER_WATCHER=true, the server does not watch project files directly: it watches the sentinel file at ~/.context/.sync-trigger, and an external hook/process must touch that file to request a sync.

  Practical workarounds until the feature ships: set up an out-of-band hook that touches the sentinel file, rely on background polling, or accept a full force=true reindex. If force=true still asks on the latest version, the maintainer asked for the exact error message and MCP server logs and pointed to the project's troubleshooting guide.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Outcome unclear)

  Asked whether the tool auto-syncs after initial indexing so only changed code gets re-indexed; answered as not available yet.

  Source: https://github.com/zilliztech/claude-context/issues/238 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @giancarloerra tried on GitHub (Didn't work)

  Tried re-triggering the code index on an existing index; the tool said the index already exists and only offered force re-index, which restarts everything.

  Source: https://github.com/zilliztech/claude-context/issues/238#issuecomment-3884558229 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @dpearson2699 tried on GitHub (Partly worked)

  Ran v0.1.14 in a multi-instance stdio setup with CLAUDE_CONTEXT_BACKGROUND_SYNC=false and CLAUDE_CONTEXT_TRIGGER_WATCHER=true; found the server watches the sentinel file ~/.context/.sync-trigger and exposes no public sync tool.

  Source: https://github.com/zilliztech/claude-context/issues/238#issuecomment-4697445548 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @fdterr tried on GitHub (Outcome unclear)

  Updated to @zilliz/claude-context-mcp@latest but still got prompted for force=true; the maintainer asked for the exact error and logs before diagnosing.

  Source: https://github.com/zilliztech/claude-context/issues/238#issuecomment-4049587368 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @fdterr tried on GitHub (Outcome unclear)

  Reported having to manually update indexes after every change because auto-sync is missing.

  Source: https://github.com/zilliztech/claude-context/issues/238#issuecomment-3807710511 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport