gms-mcp 0.1.0.post1__tar.gz

gms_mcp-0.1.0.post1/.github/workflows/publish.yml

@@ -0,0 +1,58 @@
+name: Publish to PyPI
+
+concurrency:
+  group: pypi-publish
+  cancel-in-progress: false
+
+on:
+  push:
+    branches:
+      - "main"
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    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
+        run: python -m build
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/*
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+    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="$(python -c 'import tomllib, pathlib; print(tomllib.loads(pathlib.Path(\"pyproject.toml\").read_bytes())[\"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.0.post1/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.py[cod]
+*.pyo
+
+.venv/
+venv/
+.gms-mcp/
+
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+build/
+dist/
+*.egg-info/

gms_mcp-0.1.0.post1/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.0.post1/PKG-INFO

@@ -0,0 +1,83 @@
+Metadata-Version: 2.4
+Name: gms-mcp
+Version: 0.1.0.post1
+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
+```
+
+## 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
+```
+
+## 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.0.post1/README.md

@@ -0,0 +1,60 @@
+# 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
+```
+
+## 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
+```
+
+## 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.0.post1/RELEASING.md

@@ -0,0 +1,47 @@
+# Releasing `gms-mcp`
+
+This project uses `setuptools-scm` to generate the package version from git tags.
+
+- Tag releases like `v0.1.0`, `v0.2.0`, etc.
+- Commits after a tag become automatic post-releases, e.g. `0.1.0.post3`.
+  This supports publishing on every `main` commit without manually bumping versions.
+
+## One-time: install tooling
+
+```bash
+python -m pip install -U build twine
+```
+
+## Local build
+
+```bash
+python -m build
+```
+
+Artifacts are created in `dist/`.
+
+## Publish to PyPI
+
+```bash
+twine upload dist/*
+```
+
+### First publish helper scripts
+
+- Windows: `scripts/first_pypi_upload.ps1`
+- macOS/Linux: `scripts/first_pypi_upload.sh`
+
+These build, validate, and upload from `dist/` using a PyPI API token.
+
+## Recommended: GitHub “Trusted Publishing”
+
+This repo can publish to PyPI via GitHub Actions without storing an API token.
+
+High level steps:
+1. Create the project on PyPI (`gms-mcp`).
+2. In PyPI → “Publishing” → “Trusted publishers”, add this GitHub repo and workflow.
+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.

gms_mcp-0.1.0.post1/cli/__init__.py

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

gms_mcp-0.1.0.post1/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)
+
+
+
+
+
+
+
+
+