FlureeLabs

fluree memory mcp-install

Install MCP configuration for an IDE so its agent can use memory tools.

fluree memory mcp-install [--ide <IDE>]

Options

OptionDescription
--ide <IDE>Target IDE (auto-detected if omitted)

Supported IDEs

ValueConfig writtenExtras
claude-codeclaude mcp add → ~/.claude.json (local scope)Appends to CLAUDE.md
vscode<repo>/.vscode/mcp.json (key: servers).vscode/fluree_rules.md
cursor<repo>/.cursor/mcp.json (key: mcpServers).cursor/rules/fluree_rules.md
windsurf~/.codeium/windsurf/mcp_config.json (global)—
zed<repo>/.zed/settings.json (key: context_servers)Skips if JSONC detected

Legacy aliases: claude-vscode and github-copilot both map to vscode.

When --ide is omitted, the first unconfigured detected tool is used; defaults to claude-code if nothing's detected.

Example

fluree memory mcp-install --ide cursor

Output:

  Installed: .cursor/mcp.json
  Installed: .cursor/rules/fluree_rules.md

Per-IDE config shape

The JSON mcp-install writes differs per IDE:

Cursor (.cursor/mcp.json) is the only target that sets FLUREE_HOME by default. It uses ${workspaceFolder} interpolation to pin the memory store to the current workspace regardless of where Cursor spawns the process from:

{
  "mcpServers": {
    "fluree-memory": {
      "type": "stdio",
      "command": "fluree",
      "args": ["mcp", "serve", "--transport", "stdio"],
      "env": { "FLUREE_HOME": "${workspaceFolder}/.fluree" }
    }
  }
}

VS Code, Windsurf, Zed, Claude Code get a simpler entry with no env:

{
  "command": "fluree",
  "args": ["mcp", "serve", "--transport", "stdio"]
}

(The top-level wrapper key differs — servers for VS Code, mcpServers for Windsurf, context_servers for Zed. Claude Code's entry is registered globally via claude mcp add.)

These rely on the MCP server's walk-up behavior: on start, it looks for .fluree/ beginning at its spawn CWD. That's usually the workspace, but if the IDE starts it elsewhere memory may land in a global store. See the troubleshooting section below.

Troubleshooting: repo vs global memory

Repo-scoped (the goal):

  • Memories: <repo>/.fluree-memory/repo.ttl
  • MCP log: <repo>/.fluree-memory/.local/mcp.log (truncated on each server start — tail it while reproducing the issue)

Global (something's wrong):

  • Memories under the platform default, e.g. ~/Library/Application Support/fluree/ on macOS
  • Fix: add an explicit absolute FLUREE_HOME to the MCP config entry, pointing at your repo's .fluree/, and fully restart (not just reload) the IDE. For Cursor, the ${workspaceFolder}-based default should already be in place — re-run mcp-install from inside the repo if it's missing.

See also