gms-mcp 0.1.9.dev2300__tar.gz

gms_mcp-0.1.9.dev2300/.github/workflows/publish.yml

@@ -0,0 +1,101 @@
+name: Publish to PyPI
+
+concurrency:
+  group: pypi-publish
+  cancel-in-progress: false
+
+permissions:
+  contents: read
+
+on:
+  push:
+    branches:
+      - "main"
+      - "dev"
+      - "prerelease"
+    tags:
+      - "v*"
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Publish a packaging-only post-release (example: 0.1.0.post1)"
+        required: false
+        type: string
+
+jobs:
+  compute:
+    runs-on: ubuntu-latest
+    outputs:
+      version: ${{ steps.ver.outputs.version }}
+      should_publish: ${{ steps.ver.outputs.should_publish }}
+      reason: ${{ steps.ver.outputs.reason }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install version tooling
+        run: python -m pip install -U packaging
+      - name: Compute version
+        id: ver
+        env:
+          VERSION_OVERRIDE: ${{ inputs.version }}
+        run: python scripts/ci_version.py
+      - name: Summary
+        run: |
+          echo "version=${{ steps.ver.outputs.version }}"
+          echo "should_publish=${{ steps.ver.outputs.should_publish }}"
+          echo "reason=${{ steps.ver.outputs.reason }}"
+
+  build:
+    needs: compute
+    if: needs.compute.outputs.should_publish == 'true'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install build tooling
+        run: python -m pip install -U build
+      - name: Build
+        env:
+          SETUPTOOLS_SCM_PRETEND_VERSION: ${{ needs.compute.outputs.version }}
+        run: python -m build
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/*
+
+  publish:
+    needs: [compute, build]
+    if: needs.compute.outputs.should_publish == 'true'
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist
+      - name: Verify PyPI project exists
+        shell: bash
+        run: |
+          set -euo pipefail
+          PROJECT="$(python3 -c 'import tomllib, pathlib; print(tomllib.load(pathlib.Path("pyproject.toml").open("rb"))["project"]["name"])')"
+          CODE="$(curl -sS -o /dev/null -w "%{http_code}" "https://pypi.org/pypi/${PROJECT}/json" || true)"
+          if [ "${CODE}" != "200" ]; then
+            echo "::error::PyPI project '${PROJECT}' does not exist yet (HTTP ${CODE})."
+            echo "::error::You must do the first upload manually (user identity) before Trusted Publishing can work."
+            echo "::error::Run scripts/first_pypi_upload.ps1 (Windows) or scripts/first_pypi_upload.sh (macOS/Linux)."
+            exit 1
+          fi
+      - name: Publish to PyPI (Trusted Publishing)
+        uses: pypa/gh-action-pypi-publish@release/v1

gms_mcp-0.1.9.dev2300/.gitignore

@@ -0,0 +1,20 @@
+__pycache__/
+*.py[cod]
+*.pyo
+
+.venv/
+venv/
+.gms-mcp/
+
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+build/
+dist/
+*.egg-info/
+
+gamemaker/
+.vscode/settings.json
+.cursor/mcp.json
+.cursor/debug.log

gms_mcp-0.1.9.dev2300/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [Unreleased]
+
+### Fixed
+- **Output Encoding**: Corrected a bug in `utils.py` where the UTF-8 fallback wrapper failed to reassign `sys.stdout` and `sys.stderr` on older Windows systems, ensuring Unicode-safe console output.
+- **MCP Stdio Deadlocks**: Resolved "silent hangs" in Cursor by isolating subprocess stdin (`DEVNULL`) and disabling streaming logs (`ctx.log()`) during active execution.
+- **Windows Performance**: Defaulted to in-process execution for MCP tools, making them near-instant on Windows and bypassing shim/wrapper overhead.
+- **Asset Creation Defaults**: Assets created without an explicit `parent_path` now correctly default to the project root (mirroring GameMaker IDE behavior).
+- **Invalid Room Schema**: Fixed invalid JSON generation for room `.yy` files by ensuring all 8 view slots include required fields (`hborder`, `objectId`, etc.).
+- **FastMCP Parameter Conflict**: Renamed `constructor` parameter to `is_constructor` in `gm_create_script` to resolve internal naming conflicts in FastMCP.
+
+### Changed
+- **Project Root Resolution**: Standardized environment variable support across MCP server and CLI tools. Both now consistently check for `GM_PROJECT_ROOT` followed by `PROJECT_ROOT`, improving consistency when running in different environments.
+- MCP tools now default to `skip_maintenance=True` and `maintenance_verbose=False` for faster feedback loops.
+- `gm_maintenance_dedupe_resources` now defaults to `auto=True` to prevent interactive prompt hangs.
+- Removed legacy `test_mcp_streaming_runner.py` in favor of the more stable direct/non-streaming architecture.
+- CLI test suite now imports `gms_helpers` directly from `src` and uses module invocation, removing legacy shim modules.

gms_mcp-0.1.9.dev2300/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2025 Ampersand Game Studios
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

gms_mcp-0.1.9.dev2300/PKG-INFO

@@ -0,0 +1,123 @@
+Metadata-Version: 2.4
+Name: gms-mcp
+Version: 0.1.9.dev2300
+Summary: GameMaker CLI + MCP server toolset
+Author: Callum Lory, Ampersand Game Studios
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Ampersand-Game-Studios/gms-mcp
+Project-URL: Repository, https://github.com/Ampersand-Game-Studios/gms-mcp
+Project-URL: Issues, https://github.com/Ampersand-Game-Studios/gms-mcp/issues
+Keywords: gamemaker,mcp,cursor,cli,tools
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: mcp>=1.0.0
+Dynamic: license-file
+
+# GameMaker MCP Tools
+
+This repo provides:
+- `gms`: a Python CLI for GameMaker project operations (asset creation, maintenance, runner, etc).
+- `gms-mcp`: an MCP server that exposes the same operations as MCP tools (Cursor is the primary example client).
+- `gms-mcp-init`: generates shareable MCP config files for a workspace.
+
+## Install (recommended: pipx)
+
+```powershell
+pipx install gms-mcp
+```
+
+## Local Development Setup
+
+If you are working on the `gms-mcp` codebase itself, follow these steps to set up a local development environment:
+
+1.  **Clone and install in editable mode**:
+    ```powershell
+    git checkout dev
+    pip install -e .
+    ```
+
+2.  **Initialize local and global MCP servers for testing**:
+    We recommend setting up two separate MCP server configurations in Cursor to test your changes:
+    
+    *   **Global (`gms-global`)**: For general use across all your GameMaker projects.
+    *   **Local (`gms-local`)**: Specifically for testing your current changes to the server.
+
+    Run these commands from the project root:
+    ```powershell
+    # Global setup (names it 'gms-global' in Cursor)
+    gms-mcp-init --cursor-global --server-name gms-global --mode python-module --python python --non-interactive
+
+    # Local setup (names it 'gms-local' in Cursor)
+    gms-mcp-init --cursor --server-name gms-local --mode python-module --python python --non-interactive
+    ```
+
+3.  **Verify in Cursor**:
+    Go to **Cursor Settings > Features > MCP** to see your new servers. You may need to click "Reload" or restart Cursor to see changes.
+
+## Publishing (maintainers)
+
+Publishing is automated via GitHub Actions (PyPI Trusted Publishing) on every push to `main` and on tags `v*`.
+See `RELEASING.md` for the one-time PyPI setup and the first manual upload helper scripts.
+
+## Use with a GameMaker project (multi-project friendly)
+
+Run this inside each GameMaker project workspace (or repo) to generate config:
+
+```powershell
+gms-mcp-init --cursor
+```
+
+This writes `.cursor/mcp.json` and attempts to auto-detect the `.yyp` location to set `GM_PROJECT_ROOT`.
+
+For a one-time setup that works across many projects, write Cursor's global config instead:
+
+```powershell
+gms-mcp-init --cursor-global
+```
+
+Generate example configs for other MCP-capable clients:
+
+```powershell
+gms-mcp-init --vscode --windsurf --antigravity
+```
+
+Or generate everything at once:
+
+```powershell
+gms-mcp-init --all
+```
+
+## Monorepos / multiple `.yyp`
+
+If multiple `.yyp` projects are detected in a workspace:
+- `gms-mcp-init` will warn and (when interactive) prompt you to pick one.
+- In non-interactive environments, it defaults `GM_PROJECT_ROOT` to `${workspaceFolder}` (safe).
+
+Force a specific project root:
+
+```powershell
+gms-mcp-init --cursor --gm-project-root path\\to\\project
+```
+
+Preview output without writing files:
+
+```powershell
+gms-mcp-init --cursor --dry-run
+```
+
+## CLI usage
+
+Run from a project directory (or pass `--project-root`):
+
+```powershell
+gms --version
+gms --project-root . asset create script my_function --parent-path "folders/Scripts.yy"
+```

gms_mcp-0.1.9.dev2300/README.md

@@ -0,0 +1,100 @@
+# GameMaker MCP Tools
+
+This repo provides:
+- `gms`: a Python CLI for GameMaker project operations (asset creation, maintenance, runner, etc).
+- `gms-mcp`: an MCP server that exposes the same operations as MCP tools (Cursor is the primary example client).
+- `gms-mcp-init`: generates shareable MCP config files for a workspace.
+
+## Install (recommended: pipx)
+
+```powershell
+pipx install gms-mcp
+```
+
+## Local Development Setup
+
+If you are working on the `gms-mcp` codebase itself, follow these steps to set up a local development environment:
+
+1.  **Clone and install in editable mode**:
+    ```powershell
+    git checkout dev
+    pip install -e .
+    ```
+
+2.  **Initialize local and global MCP servers for testing**:
+    We recommend setting up two separate MCP server configurations in Cursor to test your changes:
+    
+    *   **Global (`gms-global`)**: For general use across all your GameMaker projects.
+    *   **Local (`gms-local`)**: Specifically for testing your current changes to the server.
+
+    Run these commands from the project root:
+    ```powershell
+    # Global setup (names it 'gms-global' in Cursor)
+    gms-mcp-init --cursor-global --server-name gms-global --mode python-module --python python --non-interactive
+
+    # Local setup (names it 'gms-local' in Cursor)
+    gms-mcp-init --cursor --server-name gms-local --mode python-module --python python --non-interactive
+    ```
+
+3.  **Verify in Cursor**:
+    Go to **Cursor Settings > Features > MCP** to see your new servers. You may need to click "Reload" or restart Cursor to see changes.
+
+## Publishing (maintainers)
+
+Publishing is automated via GitHub Actions (PyPI Trusted Publishing) on every push to `main` and on tags `v*`.
+See `RELEASING.md` for the one-time PyPI setup and the first manual upload helper scripts.
+
+## Use with a GameMaker project (multi-project friendly)
+
+Run this inside each GameMaker project workspace (or repo) to generate config:
+
+```powershell
+gms-mcp-init --cursor
+```
+
+This writes `.cursor/mcp.json` and attempts to auto-detect the `.yyp` location to set `GM_PROJECT_ROOT`.
+
+For a one-time setup that works across many projects, write Cursor's global config instead:
+
+```powershell
+gms-mcp-init --cursor-global
+```
+
+Generate example configs for other MCP-capable clients:
+
+```powershell
+gms-mcp-init --vscode --windsurf --antigravity
+```
+
+Or generate everything at once:
+
+```powershell
+gms-mcp-init --all
+```
+
+## Monorepos / multiple `.yyp`
+
+If multiple `.yyp` projects are detected in a workspace:
+- `gms-mcp-init` will warn and (when interactive) prompt you to pick one.
+- In non-interactive environments, it defaults `GM_PROJECT_ROOT` to `${workspaceFolder}` (safe).
+
+Force a specific project root:
+
+```powershell
+gms-mcp-init --cursor --gm-project-root path\\to\\project
+```
+
+Preview output without writing files:
+
+```powershell
+gms-mcp-init --cursor --dry-run
+```
+
+## CLI usage
+
+Run from a project directory (or pass `--project-root`):
+
+```powershell
+gms --version
+gms --project-root . asset create script my_function --parent-path "folders/Scripts.yy"
+```

gms_mcp-0.1.9.dev2300/RELEASING.md

@@ -0,0 +1,52 @@
+# Releasing `gms-mcp`
+
+This project uses `setuptools-scm` + CI to control versions.
+
+Policy:
+- `main` publishes a **normal release** and bumps **patch** automatically (`X.Y.Z`).
+- `dev` publishes **dev releases** (`X.Y.(Z+1).devN`).
+- `prerelease` publishes **release candidates** (`X.Y.(Z+1)rcN`).
+- **Post releases** (`X.Y.Z.postN`) are **manual only** and intended for packaging/deployment fixes (not code changes).
+
+## One-time: install tooling
+
+```bash
+python -m pip install -U build twine
+```
+
+## Local build
+
+```bash
+python -m build
+```
+
+Artifacts are created in `dist/`.
+
+## First publish (manual)
+
+PyPI Trusted Publishing cannot create a brand-new project: the project must exist first.
+
+- Windows: `scripts/first_pypi_upload.ps1`
+- macOS/Linux: `scripts/first_pypi_upload.sh`
+
+These scripts build, validate, and upload from `dist/` using a PyPI API token.
+
+## Ongoing publishes (automated): GitHub Trusted Publishing
+
+Once the project exists on PyPI (name is `gms-mcp`, shown as `GMS-MCP` on PyPI), configure a Trusted Publisher:
+
+1. On PyPI, open the project settings for `GMS-MCP`.
+2. Add a Trusted Publisher for:
+   - Owner: `Ampersand-Game-Studios`
+   - Repository: `gms-mcp`
+   - Workflow: `.github/workflows/publish.yml`
+   - Environment: (leave blank unless you use one)
+3. Push to `main` to publish a post-release automatically, or push a version tag like `v0.1.0` to set a new base version.
+
+Notes:
+- The GitHub Actions workflow publishes on every push to `main` (as requested). This will create many versions on PyPI.
+- If you want fewer releases, change the workflow trigger to tags-only.
+
+## Manual post-release (packaging fix only)
+
+Use GitHub Actions `workflow_dispatch` for `Publish to PyPI` and provide an explicit version like `0.1.0.post1`.

gms_mcp-0.1.9.dev2300/cli/__init__.py

@@ -0,0 +1 @@
+# CLI support utilities live under this directory.

gms_mcp-0.1.9.dev2300/cli/agent_setup.py

@@ -0,0 +1,32 @@
+#!/usr/bin/env python3
+"""
+Convenience entrypoint for setting up the `gms` command.
+
+For releases, prefer `gms` and `gms-mcp-init` entrypoints.
+"""
+
+from pathlib import Path
+import sys
+
+HERE = Path(__file__).resolve().parent
+REPO_ROOT = HERE.parent
+SRC = REPO_ROOT / "src"
+if str(SRC) not in sys.path:
+    sys.path.insert(0, str(SRC))
+
+# Re-export the full implementation so `import agent_setup` behaves like the
+# original module (some tests/importers expect helper functions to exist).
+from gms_helpers.agent_setup import *  # type: ignore  # noqa: F403,E402
+from gms_helpers.agent_setup import main as _main  # noqa: E402
+
+if __name__ == "__main__":
+    raise SystemExit(0 if _main() else 1)
+
+
+
+
+
+
+
+
+