Does not work with cursor on windows machine

[WinterQuant]

LLM is still using grep and not calling infigraph .
Tool - Cursor
Env - windows
Project is already indexed .

[abdul3asith]

I was facing the same issue with Codex, infigraph was working fine in my terminal but not codex, the issue was its MCP configuration had been written using an older format. Codex expected the newer [mcp_servers.name] format, that's why Infigraph did not appear in my codex mcp list. For now I fixed it by registering Infigraph directly through Codex.

You might be facing something similar with Cursor, infigraph may be installed and indexed, but its MCP configuration could be in the wrong file, location, or format. Check Cursor’s MCP configuration and try registering the server manually using the full path to infigraph-mcp.exe

[johnintuit]

Root cause found for the Codex case @abdul3asith described. infigraph install writes MCP config for Codex as:

[mcp]
infigraph = { command = "...", args = ["--mcp"] }

but Codex actually expects:

[mcp_servers.infigraph]
command = "..."
args = ["--mcp"]

Wrong section name (mcp vs mcp_servers) and wrong table shape (inline table vs proper sub-table) — so Codex silently never saw the entry, exactly matching what @abdul3asith found by hand. Also found and fixed: on Windows, backslash paths (C:\Users...\infigraph-mcp.exe) weren't escaped for TOML, which would have broken parsing even with the right section name.

Fixed in config_targets.rs — install_toml_target / uninstall_toml_target now emit/remove [mcp_servers.infigraph] correctly, with path escaping. Also fixed several Windows-only bugs in infigraph-mcp where the HOME env var was read directly with no USERPROFILE fallback — could break group registry lookups, mcp.log path, and instance locking on Windows.

The original Cursor report is still open — Cursor's config format (~/.cursor/mcp.json, mcpServers key) already looks correct in our code, so that one needs more info to pin down (see below).

Could you help test?

Pull latest, rebuild/reinstall, and run infigraph install again. Then:

1. For Codex: does infigraph now show up in codex mcp list?
2. For Cursor (original report): please paste the contents of %USERPROFILE%.cursor\mcp.json after install, plus the infigraph install console output — want to confirm whether it's a config-format issue like Codex's, or something else on the Cursor side.

#27 @abdul3asith @WinterQuant Could you pls test with this PR before we plan for review and release this item?

@murari316 FYI