Configureing Claude.Code issue

[adamhbz]

I'm trying to set up this up to run with Claude code.

I'm using Rider with Claude code running in the terminal within Rider.

It seems to connect and do some things but at times cannot connect and times out or is awfully slow and I wondered if this editor window where it says Claude is not configured has something to do with it.

Am I missing some steps? I would like to see the editor window say that Claude code is configured.

[Scriptwonder]

So its like Claude code, but in Rider? Hmmm, that's something new. We've never tested it before.

The "Not Configured" is for the default Claude Code, as we check if Claude Code has the server JSON injected in its MCP server param, which might be different from the Rider version of CC, so I am not sure. But if it can work, then it should be connected. So it works sometimes and doesn't work or works badly most of the time. Can you put some examples here?

I would recommend trying the manual setup mentioned in the readme and see how it works. Could be a Rider thing, but I would like to see more. If it still doesn't work, we can look into Rider's CC.

[dsarno]

@adamhbz Can you try again with the latest version of the MCP? (v2.0.0). We fixed a bunch of stability issues. If you're still seeing the problem, please let us know and tick Show Debug Logs on the MCP Editor Window in Unity and send us any available logs and other info. Thanks.

[adamhbz]

Hi im getting this error with my set up (recently changed to native install of claude code):

Claude CLI registration failed: ApplicationName='/usr/local/bin/claude', CommandLine='mcp add UnityMCP -- uv --directory "/Users/XXXXXX/Documents/_WORK/XXX/Library/PackageCache/com.coplaydev.unity-mcp@eb19b4c361d7/UnityMcpServer~/src" run server.py', CurrentDirectory='/Users/XXXXXX/Documents/_WORK/XXX', Native error= Cannot find the specified file UnityEngine.Debug:LogError (object) UnityMcpBridge.Editor.Windows.UnityMcpEditorWindow:RegisterWithClaudeCode (string) (at ./Library/PackageCache/com.coplaydev.unity-mcp@eb19b4c361d7/Editor/Windows/UnityMcpEditorWindow.cs:1475) UnityMcpBridge.Editor.Windows.UnityMcpEditorWindow:AutoFirstRunSetup () (at ./Library/PackageCache/com.coplaydev.unity-mcp@eb19b4c361d7/Editor/Windows/UnityMcpEditorWindow.cs:497) UnityMcpBridge.Editor.Windows.UnityMcpEditorWindow:OnEnable () (at ./Library/PackageCache/com.coplaydev.unity-mcp@eb19b4c361d7/Editor/Windows/UnityMcpEditorWindow.cs:72)

[dsarno]

@adamhbz -- thanks. Couple things:

1. where is your Claude code installed so we can make our detector smarter?

# 1) Find your claude + uv
which claude; claude --version
which uv; uv --version

2. Manual fix while we work on this. Again, find your Claude first

# 1) Find your claude + uv
which claude; claude --version
which uv; uv --version

# 2) Register Unity MCP with absolute uv path via shell command (adjust both paths)
claude mcp remove UnityMCP || true
claude mcp add UnityMCP -- "/opt/homebrew/bin/uv" --directory "/Users/XXXX/Documents/_WORK/XXX/Library/PackageCache/com.coplaydev.unity-mcp@eb19b4c361d7/UnityMcpServer~/src" run server.py
claude mcp list

If claude is in ~/.local/bin, you may need to symlink or update PATH; Homebrew and uv default locations are /opt/homebrew/bin and ~/.local/bin respectively.

[dsarno]

@adamhbz Oh and just to make sure, did you click Auto-Setup button in the UnityMCP editor window?

[dsarno]

@adamhbz Try to refresh the Unity MCP package via Unity Package Manager, like below. I put in some fixes that should help with this issue. Let me know if it works better. Thanks.

[dsarno]

Should work now. Will keep an eye out for corner cases

[adamhbz]

Hi, i wanted to check in and say nothing seems to have changed for me.

[dsarno]

@adamhbz Thanks for checking. I think this is actually a new issue where claude is storing its config file in a different directory now. Working on a fix. Thanks.

[adamhbz]

It is working with the settings added to the .claude.json file in the root of hte user folder but the window in unity does not look like it is.

[dsarno]

Ah good to know it's working. Yes our UI is probably not looking in the new config directory yet, so it thinks it's not configured. But if Claude sees the MCP you can at least use it. Feel free to join our discord so you can let us know if you have any other issues or of this gets fixed when I push an update in next couple days https://discord.com/channels/1330955894296543364/1402494886254739496

[dsarno]

Should work now with v3.0.2