Merge branch 'fix/installer-cleanup-v2' into feat/pre-split-edit-framing-testes

* fix/installer-cleanup-v2:
  Server: set server_version.txt to 3.0.1
  MCP: Fix macOS paths and VSCode manual setup
  refactor(installer): revert to lean installer logic from ee23346; fix macOS path via Application.platform; escape pgrep pattern
  feat(installer): rewire known configs (EditorPrefs, Cursor mcp.json) to canonical path; then remove legacy if unreferenced
  chore(version): bump server_version.txt to 3.0.5
  fix(installer): use Application.platform for OS detection; add canonical root logs; fallback to RuntimeInformation
  chore(logging): include OS and server version in MCP bridge start log
  chore(server): bump server_version.txt to 3.0.4
  bump server version
  sec(installer): escape server path in pgrep pattern to prevent injection/regex issues
  chore(editor): WriteToConfig honors pythonDir; robust config match; remove unused helpers
  fix(installer): skip legacy deletion when still referenced in prefs or Cursor config
  Improve Windsurf MCP Config (CoplayDev#231)
  feat: installer cleanup, auto-migration, logging normalization
  chore: bump version to 3.0.0
  Don't ignore the package's README (CoplayDev#230)
  Rename namespace and public facing plugin output from "Unity MCP" to "MCP for Unity" (CoplayDev#225)

# Conflicts:
#	UnityMcpBridge/Editor/Tools/ManageScript.cs
#	UnityMcpBridge/Editor/Windows/MCPForUnityEditorWindow.cs
#	UnityMcpBridge/UnityMcpServer~/src/server.py
#	UnityMcpBridge/UnityMcpServer~/src/tools/__init__.py
#	UnityMcpBridge/UnityMcpServer~/src/uv.lock

Author: dsarno

.gitignore

@@ -27,7 +27,6 @@ UnityMcpServer.meta
 *.asset
 UnityMcpBridge.meta
 LICENSE.meta
-README.md.meta
 CONTRIBUTING.md.meta
 
 # IDE

CursorHelp.md

@@ -1,11 +1,11 @@
 ### Cursor/VSCode/Windsurf: UV path issue on Windows (diagnosis and fix)
 
 #### The issue
-- Some Windows machines have multiple `uv.exe` locations. Our auto-config sometimes picked a less stable path, causing the MCP client to fail to launch the Unity MCP Server or for the path to be auto-rewritten on repaint/restart.
+- Some Windows machines have multiple `uv.exe` locations. Our auto-config sometimes picked a less stable path, causing the MCP client to fail to launch the MCP for Unity Server or for the path to be auto-rewritten on repaint/restart.
 
 #### Typical symptoms
-- Cursor shows the UnityMCP server but never connects or reports it “can’t start.”
-- Your `%USERPROFILE%\\.cursor\\mcp.json` flips back to a different `command` path when Unity or the Unity MCP window refreshes.
+- Cursor shows the MCP for Unity server but never connects or reports it “can’t start.”
+- Your `%USERPROFILE%\\.cursor\\mcp.json` flips back to a different `command` path when Unity or the MCP for Unity window refreshes.
 
 #### Real-world example
 - Wrong/fragile path (auto-picked):
@@ -15,13 +15,13 @@
   - `C:\Users\mrken\AppData\Local\Microsoft\WinGet\Links\uv.exe`
 
 #### Quick fix (recommended)
-1) In Unity: `Window > Unity MCP` → select your MCP client (Cursor or Windsurf)
-2) If you see “uv Not Found,” click “Choose UV Install Location” and browse to:
+1) In MCP for Unity: `Window > MCP for Unity` → select your MCP client (Cursor or Windsurf)
+2) If you see “uv Not Found,” click “Choose `uv` Install Location” and browse to:
    - `C:\Users\<YOU>\AppData\Local\Microsoft\WinGet\Links\uv.exe`
-3) If uv is already found but wrong, still click “Choose UV Install Location” and select the `Links\uv.exe` path above. This saves a persistent override.
+3) If uv is already found but wrong, still click “Choose `uv` Install Location” and select the `Links\uv.exe` path above. This saves a persistent override.
 4) Click “Auto Configure” (or re-open the client) and restart Cursor.
 
-This sets an override stored in the Editor (key: `UnityMCP.UvPath`) so UnityMCP won’t auto-rewrite the config back to a different `uv.exe` later.
+This sets an override stored in the Editor (key: `MCPForUnity.UvPath`) so MCP for Unity won’t auto-rewrite the config back to a different `uv.exe` later.
 
 #### Verify the fix
 - Confirm global Cursor config is at: `%USERPROFILE%\\.cursor\\mcp.json`
@@ -71,8 +71,8 @@ If that runs without error, restart Cursor and it should connect.
 
 Recommended practice
 
-- Prefer the WinGet Links shim paths above. If present, select one via “Choose UV Install Location”.
-- If the unity window keeps rewriting to a different `uv.exe`, pick the Links shim again; Unity MCP saves a pinned override and will stop auto-rewrites.
+- Prefer the WinGet Links shim paths above. If present, select one via “Choose `uv` Install Location”.
+- If the unity window keeps rewriting to a different `uv.exe`, pick the Links shim again; MCP for Unity saves a pinned override and will stop auto-rewrites.
 - If neither Links path exists, a reasonable fallback is `~/.local/bin/uv.exe` (uv tools bin) or a Scoop shim, but Links is preferred for stability.
 
 References

README-DEV.md

@@ -1,24 +1,24 @@
-# Unity MCP Development Tools
+# MCP for Unity Development Tools
 
-Welcome to the Unity MCP development environment! This directory contains tools and utilities to streamline Unity MCP core development.
+Welcome to the MCP for Unity development environment! This directory contains tools and utilities to streamline MCP for Unity core development.
 
 ## 🚀 Available Development Features
 
 ### ✅ Development Deployment Scripts
-Quick deployment and testing tools for Unity MCP core changes.
+Quick deployment and testing tools for MCP for Unity core changes.
 
 ### 🔄 Coming Soon
 - **Development Mode Toggle**: Built-in Unity editor development features
 - **Hot Reload System**: Real-time code updates without Unity restarts  
-- **Plugin Development Kit**: Tools for creating custom Unity MCP extensions
+- **Plugin Development Kit**: Tools for creating custom MCP for Unity extensions
 - **Automated Testing Suite**: Comprehensive testing framework for contributions
 - **Debug Dashboard**: Advanced debugging and monitoring tools
 
 ---
 
 ## Development Deployment Scripts
 
-These deployment scripts help you quickly test changes to Unity MCP core code.
+These deployment scripts help you quickly test changes to MCP for Unity core code.
 
 ## Scripts
 
@@ -60,7 +60,7 @@ X:\UnityProject\Library\PackageCache\com.coplaydev.unity-mcp@272123cfd97e
 
 To find it reliably:
 1. Open Unity Package Manager
-2. Select "Unity MCP" package
+2. Select "MCP for Unity" package
 3. Right click the package and choose "Show in Explorer"
 4. That opens the exact cache folder Unity is using for your project
 
@@ -77,7 +77,7 @@ Note: In recent builds, the Python server sources are also bundled inside the pa
 
 ## Switching MCP package sources quickly
 
-Use `mcp_source.py` to quickly switch between different Unity MCP package sources:
+Use `mcp_source.py` to quickly switch between different MCP for Unity package sources:
 
 **Usage:**
 ```bash
@@ -96,7 +96,7 @@ After switching, open Package Manager and Refresh to re-resolve packages.
 
 ### "Path not found" errors running the .bat file
 - Verify Unity package cache path is correct
-- Check that Unity MCP package is actually installed
+- Check that MCP for Unity package is actually installed
 - Ensure server is installed via MCP client
 
 ### "Permission denied" errors
@@ -110,4 +110,4 @@ After switching, open Package Manager and Refresh to re-resolve packages.
 - Verify backup directory path is correct
 
 ### Windows uv path issues
-- On Windows, when testing GUI clients, prefer the WinGet Links `uv.exe`; if multiple `uv.exe` exist, use "Choose UV Install Location" to pin the Links shim.
+- On Windows, when testing GUI clients, prefer the WinGet Links `uv.exe`; if multiple `uv.exe` exist, use "Choose `uv` Install Location" to pin the Links shim.

README.md

@@ -1,4 +1,4 @@
-# Unity MCP ✨
+# MCP for Unity ✨
 
 #### Proudly sponsored and maintained by [Coplay](https://www.coplay.dev/?ref=unity-mcp), the AI assistant for Unity. [Read the backstory here.](https://www.coplay.dev/blog/coplay-and-open-source-unity-mcp-join-forces)
 
@@ -13,13 +13,13 @@
 
 **Create your Unity apps with LLMs!**
 
-Unity MCP acts as a bridge, allowing AI assistants (like Claude, Cursor) to interact directly with your Unity Editor via a local **MCP (Model Context Protocol) Client**. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
+MCP for Unity acts as a bridge, allowing AI assistants (like Claude, Cursor) to interact directly with your Unity Editor via a local **MCP (Model Context Protocol) Client**. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
 
 ## 💬 Join Our Community
 
 ### [Discord](https://discord.gg/y4p8KfzrN4)
 
-**Get help, share ideas, and collaborate with other Unity MCP developers!**  
+**Get help, share ideas, and collaborate with other MCP for Unity developers!**  
 
 ---
 
@@ -49,12 +49,12 @@ Unity MCP acts as a bridge, allowing AI assistants (like Claude, Cursor) to inte
 
 ## How It Works 🤔
 
-Unity MCP connects your tools using two components:
+MCP for Unity connects your tools using two components:
 
-1.  **Unity MCP Bridge:** A Unity package running inside the Editor. (Installed via Package Manager).
-2.  **Unity MCP Server:** A Python server that runs locally, communicating between the Unity Bridge and your MCP Client. (Installed manually).
+1.  **MCP for Unity Bridge:** A Unity package running inside the Editor. (Installed via Package Manager).
+2.  **MCP for Unity Server:** A Python server that runs locally, communicating between the Unity Bridge and your MCP Client. (Installed automatically by the package on first run or via Auto-Setup; manual setup is available as a fallback).
 
-**Flow:** `[Your LLM via MCP Client] <-> [Unity MCP Server (Python)] <-> [Unity MCP Bridge (Unity Editor)]`
+**Flow:** `[Your LLM via MCP Client] <-> [MCP for Unity Server (Python)] <-> [MCP for Unity Bridge (Unity Editor)]`
 
 ---
 
@@ -111,7 +111,7 @@ Unity MCP connects your tools using two components:
     https://github.com/CoplayDev/unity-mcp.git?path=/UnityMcpBridge
     ```
 5.  Click `Add`.
-6. The MCP Server should automatically be installed onto your machine as a result of this process.
+6. The MCP server is installed automatically by the package on first run or via Auto-Setup. If that fails, use Manual Configuration (below).
 
 #### To install via OpenUPM
 
@@ -123,20 +123,20 @@ Unity MCP connects your tools using two components:
 
 ### Step 2: Configure Your MCP Client
 
-Connect your MCP Client (Claude, Cursor, etc.) to the Python server you installed in Step 1.
+Connect your MCP Client (Claude, Cursor, etc.) to the Python server set up in Step 1 (auto) or via Manual Configuration (below).
 
-<img width="648" height="599" alt="UnityMCP-Readme-Image" src="https://github.com/user-attachments/assets/b4a725da-5c43-4bd6-80d6-ee2e3cca9596" />
+<img width="648" height="599" alt="MCPForUnity-Readme-Image" src="https://github.com/user-attachments/assets/b4a725da-5c43-4bd6-80d6-ee2e3cca9596" />
 
 **Option A: Auto-Setup (Recommended for Claude/Cursor/VSC Copilot)**
 
-1.  In Unity, go to `Window > Unity MCP`.
+1.  In Unity, go to `Window > MCP for Unity`.
 2.  Click `Auto-Setup`.
 3.  Look for a green status indicator 🟢 and "Connected ✓". *(This attempts to modify the MCP Client\'s config file automatically).* 
 
 <details><summary><strong>Client-specific troubleshooting</strong></summary>
 
-  - **VSCode**: uses `Code/User/mcp.json` with top-level `servers.unityMCP` and `"type": "stdio"`. On Windows, Unity MCP writes an absolute `uv.exe` (prefers WinGet Links shim) to avoid PATH issues.
-  - **Cursor / Windsurf** [(**help link**)](https://github.com/CoplayDev/unity-mcp/wiki/1.-Fix-Unity-MCP-and-Cursor,-VSCode-&-Windsurf): if `uv` is missing, the Unity MCP window shows "uv Not Found" with a quick [HELP] link and a "Choose UV Install Location" button.
+  - **VSCode**: uses `Code/User/mcp.json` with top-level `servers.unityMCP` and `"type": "stdio"`. On Windows, MCP for Unity writes an absolute `uv.exe` (prefers WinGet Links shim) to avoid PATH issues.
+  - **Cursor / Windsurf** [(**help link**)](https://github.com/CoplayDev/unity-mcp/wiki/1.-Fix-Unity-MCP-and-Cursor,-VSCode-&-Windsurf): if `uv` is missing, the MCP for Unity window shows "uv Not Found" with a quick [HELP] link and a "Choose `uv` Install Location" button.
   - **Claude Code** [(**help link**)](https://github.com/CoplayDev/unity-mcp/wiki/2.-Fix-Unity-MCP-and-Claude-Code): if `claude` isn't found, the window shows "Claude Not Found" with [HELP] and a "Choose Claude Location" button. Unregister now updates the UI immediately.</details>
 
 
@@ -252,9 +252,9 @@ claude mcp add UnityMCP -- "C:/Users/USERNAME/AppData/Roaming/Python/Python313/S
 
 ## Usage ▶️
 
-1. **Open your Unity Project.** The Unity MCP Bridge (package) should connect automatically. Check status via Window > Unity MCP.
+1. **Open your Unity Project.** The MCP for Unity package should connect automatically. Check status via Window > MCP for Unity.
 
-2. **Start your MCP Client** (Claude, Cursor, etc.). It should automatically launch the Unity MCP Server (Python) using the configuration from Installation Step 3.
+2. **Start your MCP Client** (Claude, Cursor, etc.). It should automatically launch the MCP for Unity Server (Python) using the configuration from Installation Step 2.
 
 3. **Interact!** Unity tools should now be available in your MCP Client.
 
@@ -304,9 +304,9 @@ claude mcp add UnityMCP -- "C:/Users/USERNAME/AppData/Roaming/Python/Python313/S
 
 ### Development Tools
 
-If you\'re contributing to Unity MCP or want to test core changes, we have development tools to streamline your workflow:
+If you\'re contributing to MCP for Unity or want to test core changes, we have development tools to streamline your workflow:
 
-- **Development Deployment Scripts**: Quickly deploy and test your changes to Unity MCP Bridge and Python Server
+- **Development Deployment Scripts**: Quickly deploy and test your changes to MCP for Unity Bridge and Python Server
 - **Automatic Backup System**: Safe testing with easy rollback capabilities  
 - **Hot Reload Workflow**: Fast iteration cycle for core development
 - **More coming!**
@@ -315,7 +315,7 @@ If you\'re contributing to Unity MCP or want to test core changes, we have devel
 
 ### Contributing 🤝
 
-Help make Unity MCP better!
+Help make MCP for Unity better!
 
 1. **Fork** the main repository.
 
@@ -338,7 +338,7 @@ Help make Unity MCP better!
 
 - **Unity Bridge Not Running/Connecting:**
     - Ensure Unity Editor is open.
-    - Check the status window: Window > Unity MCP.
+    - Check the status window: Window > MCP for Unity.
     - Restart Unity.
 - **MCP Client Not Connecting / Server Not Starting:**
     - **Verify Server Path:** Double-check the --directory path in your MCP Client\'s JSON config. It must exactly match the location where you cloned the UnityMCP repository in Installation Step 1 (e.g., .../Programs/UnityMCP/UnityMcpServer/src).

TestProjects/UnityMCPTests/Assets/Tests/EditMode/UnityMCPTests.EditMode.asmdef renamed to TestProjects/UnityMCPTests/Assets/Tests/EditMode/MCPForUnityTests.Editor.asmdef

@@ -1,8 +1,8 @@
 {
-  "name": "UnityMCPTests.EditMode",
+  "name": "MCPForUnityTests.EditMode",
   "rootNamespace": "",
   "references": [
-    "UnityMcpBridge.Editor",
+    "MCPForUnity.Editor",
     "UnityEngine.TestRunner",
     "UnityEditor.TestRunner"
   ],

UnityMcpBridge/Runtime/UnityMcpBridge.Runtime.asmdef.meta renamed to TestProjects/UnityMCPTests/Assets/Tests/EditMode/MCPForUnityTests.Editor.asmdef.meta

@@ -1,9 +1,9 @@
 using System;
 using Newtonsoft.Json;
 using NUnit.Framework;
-using UnityMcpBridge.Editor.Tools;
+using MCPForUnity.Editor.Tools;
 
-namespace UnityMCPTests.EditMode
+namespace MCPForUnityTests.Editor.Tools
 {
     public class CommandRegistryTests
     {