minecode-mcp 0.2.1__tar.gz → 0.2.2__tar.gz

{minecode_mcp-0.2.1 → minecode_mcp-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: minecode-mcp
-Version: 0.2.1
+Version: 0.2.2
 Summary: MCP Server for Minecraft datapack development with wiki, Spyglass, Misode, and Mojira integrations
 Project-URL: Homepage, https://github.com/AnCarsenat/minecode-mcp
 Project-URL: Repository, https://github.com/AnCarsenat/minecode-mcp
@@ -244,7 +244,8 @@ Configure your client (next section), then restart it. The client spawns the ser
 | Symptom | Cause and fix |
 |---------|---------------|
 | `command not found: minecode` | The script isn't on PATH. Use `python -m minecode.server`, or check `pip show -f minecode-mcp` |
-| `No module named minecode` | Wrong interpreter. Use the same Python you installed into — in a venv, use its absolute path in the client config |
+| `No module named minecode` | Wrong interpreter. The client's `python` isn't the one you installed into — classic with pipx and venv installs. Use `"command": "minecode"` in the client config, or the interpreter's absolute path |
+| `Error while finding module specification for 'minecode'` | `-m minecode` is not a valid entry point. The module form is `-m minecode.server` |
 | `AttributeError: 'Server' object has no attribute 'list_tools'` | You have mcp 2.x. Run `pip install "mcp>=1.25.0,<2"` |
 | Server starts, client shows no tools | Client config points at a different Python or a stale install. Restart the client fully — most only read MCP config at startup |
 | Everything hangs with no output | Expected when run directly, see above. If it happens *inside a client*, check the client's MCP logs |
@@ -277,6 +278,23 @@ Configure your client (next section), then restart it. The client spawns the ser
 
 Add to **User Settings** (`Ctrl+Shift+P` → "MCP: Open User Configuration"), or create `.vscode/mcp.json` in your workspace:
 
+```json
+{
+  "servers": {
+    "minecode": {
+      "type": "stdio",
+      "command": "minecode",
+      "args": []
+    }
+  },
+  "inputs": []
+}
+```
+
+The `minecode` script is installed alongside the package and already points at the right interpreter, so this form works for pipx, venv, and `--user` installs alike.
+
+The module form is equivalent **only if the package is importable from whichever `python` the client resolves**:
+
 ```json
 {
   "servers": {
@@ -290,7 +308,9 @@ Add to **User Settings** (`Ctrl+Shift+P` → "MCP: Open User Configuration"), or
 }
 ```
 
-> On Windows use `"command": "py"`. `py` is the Windows launcher and does not exist on macOS or Linux.
+> ⚠️ VS Code spawns the server with a bare `python` from `PATH` — **not** your selected Python interpreter, and not a pipx or venv environment. With a pipx install this fails with `No module named minecode`, since the package lives in pipx's own venv. Use `"command": "minecode"` above, or the absolute interpreter path from the next section.
+
+> On Windows use `"command": "py"` for the module form. `py` is the Windows launcher and does not exist on macOS or Linux.
 
 ### If `minecode` isn't on PATH
 

{minecode_mcp-0.2.1 → minecode_mcp-0.2.2}/README.md

@@ -215,7 +215,8 @@ Configure your client (next section), then restart it. The client spawns the ser
 | Symptom | Cause and fix |
 |---------|---------------|
 | `command not found: minecode` | The script isn't on PATH. Use `python -m minecode.server`, or check `pip show -f minecode-mcp` |
-| `No module named minecode` | Wrong interpreter. Use the same Python you installed into — in a venv, use its absolute path in the client config |
+| `No module named minecode` | Wrong interpreter. The client's `python` isn't the one you installed into — classic with pipx and venv installs. Use `"command": "minecode"` in the client config, or the interpreter's absolute path |
+| `Error while finding module specification for 'minecode'` | `-m minecode` is not a valid entry point. The module form is `-m minecode.server` |
 | `AttributeError: 'Server' object has no attribute 'list_tools'` | You have mcp 2.x. Run `pip install "mcp>=1.25.0,<2"` |
 | Server starts, client shows no tools | Client config points at a different Python or a stale install. Restart the client fully — most only read MCP config at startup |
 | Everything hangs with no output | Expected when run directly, see above. If it happens *inside a client*, check the client's MCP logs |
@@ -248,6 +249,23 @@ Configure your client (next section), then restart it. The client spawns the ser
 
 Add to **User Settings** (`Ctrl+Shift+P` → "MCP: Open User Configuration"), or create `.vscode/mcp.json` in your workspace:
 
+```json
+{
+  "servers": {
+    "minecode": {
+      "type": "stdio",
+      "command": "minecode",
+      "args": []
+    }
+  },
+  "inputs": []
+}
+```
+
+The `minecode` script is installed alongside the package and already points at the right interpreter, so this form works for pipx, venv, and `--user` installs alike.
+
+The module form is equivalent **only if the package is importable from whichever `python` the client resolves**:
+
 ```json
 {
   "servers": {
@@ -261,7 +279,9 @@ Add to **User Settings** (`Ctrl+Shift+P` → "MCP: Open User Configuration"), or
 }
 ```
 
-> On Windows use `"command": "py"`. `py` is the Windows launcher and does not exist on macOS or Linux.
+> ⚠️ VS Code spawns the server with a bare `python` from `PATH` — **not** your selected Python interpreter, and not a pipx or venv environment. With a pipx install this fails with `No module named minecode`, since the package lives in pipx's own venv. Use `"command": "minecode"` above, or the absolute interpreter path from the next section.
+
+> On Windows use `"command": "py"` for the module form. `py` is the Windows launcher and does not exist on macOS or Linux.
 
 ### If `minecode` isn't on PATH
 

{minecode_mcp-0.2.1 → minecode_mcp-0.2.2}/pyproject.toml

@@ -10,7 +10,7 @@ name = "minecode-mcp"
 # so a forgotten bump fails loudly instead of shipping a mislabelled release.
 # PyPI version numbers are permanent -- a published version can never be
 # replaced, only superseded. See "Releasing" in README.md.
-version = "0.2.1"
+version = "0.2.2"
 description = "MCP Server for Minecraft datapack development with wiki, Spyglass, Misode, and Mojira integrations"
 readme = "README.md"
 license = "MIT"