Remove legacy MCP/ folder and update all references

- Delete MCP/ directory (replaced by unrealmcp/ pip package)
- Update README: architecture, file structure, install steps, custom tools
- Update CONTRIBUTING.md: development setup with pip install -e .,
  testing workflow, adding new tools, running linter and CI locally
- Update CI: remove MCP/ lint and import checks
- Single source of truth is now unrealmcp/ package

Author: aadeshrao123

.github/workflows/ci.yml

@@ -27,10 +27,6 @@ jobs:
           python -m pip install --upgrade pip
           pip install ruff
 
-      - name: Lint MCP/ (legacy standalone server)
-        run: |
-          ruff check MCP/ --select=E,F,W --ignore=E501,F401
-
       - name: Lint unrealmcp/ (pip package)
         run: |
           ruff check unrealmcp/ --select=E,F,W --ignore=E501,F401
@@ -75,16 +71,6 @@ jobs:
           which unrealmcp
           unrealmcp --help || true
 
-      - name: Check MCP/ standalone still imports
-        run: |
-          cd MCP
-          python -c "
-          import sys, os
-          sys.path.insert(0, os.getcwd())
-          import _bridge
-          print('  MCP/ standalone bridge OK')
-          "
-
       - name: Verify plugin descriptor is valid JSON
         run: |
           python -c "

CONTRIBUTING.md

@@ -9,15 +9,75 @@ Found a bug or have a feature request? [Open an issue](https://github.com/aadesh
 - **Bug reports**: Steps to reproduce, expected vs actual behavior, UE version, and OS
 - **Feature requests**: What you'd like to see and why it would be useful
 
-## Pull Requests
+## Development Setup
+
+### Prerequisites
+
+- Unreal Engine 5.7 (or the version you want to test against)
+- Python 3.10+
+- Git
+
+### Getting Started
+
+1. **Fork and clone** the repository:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/Unreal-MCP.git
+   cd Unreal-MCP
+   ```
+
+2. **Install in editable mode** — this is the key step:
+   ```bash
+   pip install -e .
+   ```
+   This links the `unrealmcp` command to your local source files. Any changes you make to Python files take effect immediately — no need to reinstall or rebuild.
+
+3. **Copy or symlink the plugin** into a UE project's `Plugins/` folder so you can test the C++ bridge.
+
+4. **Open the UE project**, check the Output Log for `MCP Bridge initialized on port XXXXX`.
+
+5. **Configure your AI tool** to use `"command": "unrealmcp"` (see [README](README.md#step-2-run-the-setup-script) or run `install.bat`/`install.sh`).
+
+### Testing Your Changes
+
+Since you installed with `pip install -e .`, edits to any file in `unrealmcp/` are live instantly:
 
-Want to contribute code? Great! Here's the workflow:
+- **Edit** a file in `unrealmcp/tools/` (e.g., add a new tool or fix a bug)
+- **Restart** your AI tool (so it reconnects to the MCP server)
+- **Test** the change — no reinstall needed
+
+For C++ changes, you'll need to rebuild the plugin through your IDE (Rider, Visual Studio, etc.) and restart the editor.
+
+### Running the Linter
+
+```bash
+pip install ruff
+ruff check unrealmcp/ --select=E,F,W --ignore=E501,F401
+```
+
+### Running the CI Tests Locally
+
+```bash
+# Install and verify
+pip install -e .
+python -c "import unrealmcp; print(unrealmcp.__version__)"
+
+# Check all tool modules import
+python -c "
+from unrealmcp._bridge import mcp
+from unrealmcp.tools import core, assets, blueprints, materials
+print('All imports OK')
+"
+```
+
+## Pull Requests
 
 1. **Fork** the repository
 2. **Create a branch** from `main` (`git checkout -b my-feature`)
-3. **Make your changes** — keep commits focused and well-described
-4. **Test** your changes with a running UE5 editor
-5. **Open a Pull Request** against `main`
+3. **Install in editable mode** (`pip install -e .`)
+4. **Make your changes** — keep commits focused and well-described
+5. **Test** your changes with a running UE5 editor
+6. **Run the linter** (`ruff check unrealmcp/`)
+7. **Open a Pull Request** against `main`
 
 ### Guidelines
 
@@ -29,13 +89,31 @@ Want to contribute code? Great! Here's the workflow:
 
 ### Adding New Tools
 
-See the [Adding Custom Tools](README.md#adding-custom-tools) section in the README for the pattern. In short:
+1. Create a new file in `unrealmcp/tools/` (or add to an existing one):
+   ```python
+   from unrealmcp._bridge import mcp
+   from unrealmcp._tcp_bridge import _call
+
+   @mcp.tool()
+   def my_custom_tool(param1: str, param2: int = 10) -> str:
+       """Description shown to the AI assistant."""
+       return _call("my_custom_command", {
+           "param1": param1,
+           "param2": param2,
+       })
+   ```
+
+2. Register it in `unrealmcp/tools/__init__.py`:
+   ```python
+   from unrealmcp.tools import my_tools  # noqa: F401
+   ```
 
-1. Add a Python tool function in `MCP/tools/`
-2. Register it in `MCP/tools/__init__.py`
 3. Add the C++ command handler in `Source/UnrealMCPBridge/Private/Commands/`
+
 4. Wire it up in `ExecuteCommand()`
 
+Since you're in editable mode, the new tool is available as soon as you restart your AI tool — no pip install needed.
+
 ### What Makes a Good Contribution
 
 - Bug fixes with clear reproduction steps