Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

IDE support matrix

Where each supported AI coding tool stores its MCP config and its rules file, and whether the config is scoped per-repo or global.

IDEMCP configConfig scopeFLUREE_HOME set?Rules filemcp-install value
Claude Code~/.claude.json (via claude mcp add)user (local)nosection appended to <repo>/CLAUDE.mdclaude-code
Cursor<repo>/.cursor/mcp.jsonrepoyes — ${workspaceFolder}/.fluree<repo>/.cursor/rules/fluree_rules.mdcursor
VS Code (Copilot)<repo>/.vscode/mcp.jsonrepono<repo>/.vscode/fluree_rules.mdvscode
Windsurf~/.codeium/windsurf/mcp_config.jsonglobalnononewindsurf
Zed<repo>/.zed/settings.jsonrepononone (skipped if JSONC)zed

Legacy aliases:

  • claude-vscode → vscode
  • github-copilot → vscode

FLUREE_HOME and repo scoping

Only the Cursor config sets FLUREE_HOME automatically. For the other IDEs, the MCP server figures out which repo it’s serving by walking up from its spawn CWD until it finds a .fluree/ directory. In normal use the IDE spawns the server from the workspace root, so this works without extra configuration.

If memory ends up in a platform-global store instead of <repo>/.fluree-memory/, the fix is to add FLUREE_HOME manually to the relevant MCP config, pointing at an absolute path (or a variable the IDE interpolates — Cursor supports ${workspaceFolder}; other IDEs’ support varies). Then restart the IDE.

Detection

fluree memory init detects each IDE via four signal classes (any one is enough):

  1. Binary on PATH — claude, code, cursor, windsurf, zed. This is the most reliable cross-platform signal and the primary signal for Claude Code, which has no .app bundle.
  2. macOS app bundle — /Applications/<App>.app or ~/Applications/<App>.app.
  3. Home-dir marker — ~/.cursor, ~/.vscode, ~/.codeium/windsurf, ~/.zed, ~/.config/zed, ~/.claude, ~/.claude.json.
  4. User-config dir — <config>/Code, <config>/Cursor, <config>/Windsurf, <config>/Zed, where <config> is ~/.config (Linux), ~/Library/Application Support (macOS), or %APPDATA% (Windows). VS Code on Linux, for example, stores its first-launch marker as ~/.config/Code/, not ~/.vscode/.

A freshly installed IDE that has never been launched and isn’t on PATH may go undetected. If init misses your IDE, install MCP for it directly: fluree memory mcp-install --ide <tool>.

Known gotchas

  • Zed + JSONC: If .zed/settings.json contains // comments, mcp-install refuses to write to avoid corrupting your settings. Paste the snippet yourself or strip comments first. The same refusal now applies to .cursor/mcp.json, .vscode/mcp.json, and ~/.codeium/windsurf/mcp_config.json — any non-empty config that fails to parse as plain JSON is left alone, and mcp-install prints a snippet for you to paste in.
  • Windsurf globals: Windsurf’s MCP config is user-global, not per-repo. If you work across multiple repos, you likely need to leave FLUREE_HOME unset and rely on walk-up — or switch the env var per project manually.
  • Cursor restarts: Cursor caches MCP servers aggressively. If a change to .cursor/mcp.json doesn’t take effect, fully quit Cursor (Cmd-Q on macOS) rather than just reloading the window.
  • Claude Code CLAUDE.md: The rules section is appended at the end of <repo>/CLAUDE.md (only if one doesn’t already mention fluree memory or memory_recall). If you have a large existing CLAUDE.md, make sure the agent is actually reading to the end.
  • Running from a subdir: init resolves the project root by walking up from the cwd to the nearest .git. The Claude Code installer registers MCP keyed by that root (not by your subdir cwd), so running fluree memory init from crates/foo/ behaves identically to running it from the repo root.