ignition-mcp 0.1.0__tar.gz

ignition_mcp-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Build bridge archive
+        run: python bridge/build_zip.py
+      - name: Lint
+        run: ruff check src tests
+      - name: Format check
+        run: ruff format --check src tests
+      - name: Type check
+        run: mypy src
+      - name: Unit tests
+        run: pytest tests/unit -q

ignition_mcp-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,39 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Build bridge archive
+        run: python bridge/build_zip.py
+      - name: Install build tool
+        run: python -m pip install --upgrade build
+      - name: Build sdist and wheel
+        run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

ignition_mcp-0.1.0/.gitignore

@@ -0,0 +1,25 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.coverage
+htmlcov/
+
+# Workforce scratch (kept out of the published repo)
+tasks/
+results/
+
+# Secrets — never commit
+*.secret
+.env
+
+# OS
+.DS_Store

ignition_mcp-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 jsgorana
+
+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.

ignition_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,201 @@
+Metadata-Version: 2.4
+Name: ignition-mcp
+Version: 0.1.0
+Summary: MCP server for Inductive Automation Ignition: tags, alarms, history, projects, and full Perspective deployment
+Project-URL: Homepage, https://github.com/jsgorana/ignition-mcp
+Project-URL: Issues, https://github.com/jsgorana/ignition-mcp/issues
+Author: jsgorana
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ignition,inductive-automation,mcp,model-context-protocol,perspective,scada
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Manufacturing
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Requires-Dist: mcp>=1.2.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<!-- mcp-name: io.github.jsgorana/ignition-mcp -->
+# ignition-mcp
+
+An MCP (Model Context Protocol) server for Inductive Automation Ignition. It gives an AI
+assistant, Claude Desktop, Claude Code, or any [MCP client](https://modelcontextprotocol.io),
+structured access to an Ignition gateway: browse and write tags, query history and alarms,
+manage projects, and deploy full Perspective views.
+
+Tested against Ignition 8.3. 43 tools spanning tags, history, alarms, projects, gateway
+administration, and Perspective. The server is read-only by default; every write is gated behind
+an explicit opt-in.
+
+```
+You:    "Deploy a Perspective dashboard to a new project called LineOverview with a
+         gauge bound to [default]Line1/Speed."
+Claude: (bootstraps the project, writes the view, wires the tag binding, triggers a scan)
+        -> https://gateway:8088/data/perspective/client/LineOverview
+```
+
+## Why two planes
+
+Ignition 8.3 ships a native REST API, but it doesn't expose live tag values, tag history, alarm
+queries, or Perspective view resources. `ignition-mcp` covers the gap with two transport planes:
+
+- **REST plane.** The gateway's native `/data/api/v1` API, authenticated with an API key, used
+  for projects, gateway configuration, modules, logs, backups, and Perspective session
+  diagnostics.
+- **Bridge plane.** A small WebDev project (`mcp-bridge`) you install once on the gateway. It
+  exposes the gateway scripting surface (`system.tag.*`, `system.alarm.*`, `system.db.*`, and
+  project file I/O) over HMAC-signed HTTP requests.
+
+Tools that need the bridge degrade with a clear message if it isn't installed. Run
+`ignition_diagnose` any time to see what's configured and what's missing.
+
+## Quickstart
+
+### 1. Create an API key on the gateway
+
+Gateway web UI -> Config -> Security -> API Keys -> Create. Give it a name, for example `claude`.
+Copy the full token; it looks like `claude:AbCd...`.
+
+The key's auto-created security level (`Authenticated/<key-name>`) needs to be granted gateway
+read/write access under Config -> Security -> General -> Gateway Read/Write Permissions. Skip
+this step and calls return HTTP 403; `ignition_diagnose` will tell you and give the exact fix.
+
+### 2. Install ignition-mcp
+
+```bash
+pipx install ignition-mcp
+# or: uvx ignition-mcp
+# or: pip install ignition-mcp
+```
+
+### 3. Configure your MCP client
+
+Claude Desktop (`claude_desktop_config.json`) or Claude Code (`.mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "ignition": {
+      "command": "ignition-mcp",
+      "env": {
+        "IGNITION_URL": "http://localhost:8088",
+        "IGNITION_API_TOKEN": "claude:YOUR_SECRET_HERE"
+      }
+    }
+  }
+}
+```
+
+Restart the client and ask it to run `ignition_diagnose`. You should get an all-green checklist,
+aside from a warning about the bridge, which is the next step.
+
+### 4. Install the bridge (recommended, needed for live data and Perspective deploys)
+
+Generate a random secret, enable writes, and let the server install the bridge for you:
+
+```json
+"env": {
+  "IGNITION_URL": "http://localhost:8088",
+  "IGNITION_API_TOKEN": "claude:YOUR_SECRET_HERE",
+  "IGNITION_BRIDGE_SECRET": "a-long-random-string",
+  "IGNITION_ALLOW_WRITES": "true"
+}
+```
+
+Ask your assistant to install the bridge (this runs the `bridge_install` tool), then run
+`ignition_diagnose` again to confirm the bridge check is green. See
+[docs/bridge.md](docs/bridge.md) for the manual install path and troubleshooting.
+
+## Configuration
+
+| Variable | Required | Default | Meaning |
+|---|---|---|---|
+| `IGNITION_URL` | yes | none | Gateway base URL, e.g. `http://localhost:8088` |
+| `IGNITION_API_TOKEN` | yes | none | API key, `name:secret` |
+| `IGNITION_BRIDGE_SECRET` | no | unset | HMAC secret for the bridge; bridge tools are disabled without it |
+| `IGNITION_ALLOW_WRITES` | no | `false` | Master switch for every mutating tool |
+| `IGNITION_TLS_VERIFY` | no | `true` | Set to `false` for self-signed dev gateways |
+| `IGNITION_TIMEOUT_S` | no | `30` | Per-request timeout, in seconds |
+| `IGNITION_TAG_WRITE_ALLOWLIST` | no | unset | Comma-separated glob patterns; tag writes outside them are refused |
+
+## Safety model
+
+- Read-only by default. Mutating tools refuse to run unless `IGNITION_ALLOW_WRITES=true` and the
+  call passes `confirm=true`. Your assistant sets `confirm` after you approve the action.
+- Destructive operations echo the name back. Deleting a project or view requires re-sending its
+  exact name.
+- A tag-write allowlist lets you restrict writable tags to specific path globs.
+- REST mutations carry the API key's identity into Ignition's own audit log; bridge mutations log
+  to the `mcp-bridge` logger. Secrets are never logged or echoed back.
+- The bridge's file endpoints are confined to `data/projects/`; nothing outside that tree is
+  reachable.
+
+## Tool catalog
+
+| Area | Tools |
+|---|---|
+| Diagnostics | `ignition_diagnose`, `gateway_info`, `gateway_trial_status`, `gateway_trial_reset` |
+| Tags | `tag_browse`, `tag_read`, `tag_write`, `tag_create`, `tag_config_export`, `tag_config_import` |
+| History | `history_query`, `history_providers` |
+| Alarms | `alarm_status`, `alarm_journal`, `alarm_acknowledge` |
+| Projects | `project_list`, `project_get`, `project_create`, `project_delete`, `project_export`, `project_import`, `project_scan` |
+| Perspective | `perspective_bootstrap_project`, `perspective_list_views`, `perspective_get_view`, `perspective_upsert_view`, `perspective_delete_view`, `perspective_validate_view`, `perspective_page_config_get/set`, `perspective_session_props_get`, `perspective_style_upsert`, `perspective_list_sessions` |
+| Gateway admin | `gateway_modules`, `gateway_logs_query`, `gateway_logger_set_level`, `gateway_backup`, `gateway_performance`, `config_resource_list` |
+| Database | `db_run_named_query`, `db_query` |
+| Bridge | `bridge_install`, `bridge_status` |
+
+The server also exposes MCP resources the assistant can read to author valid Perspective views:
+`ignition://docs/view-schema` and `ignition://templates/view/{flex-basic,coordinate-basic,tag-bound-dashboard}`.
+
+## Building Perspective views
+
+See [docs/perspective-authoring.md](docs/perspective-authoring.md) for the full writeup. In
+short: the assistant reads the view-schema resource, starts from a template, validates offline
+with `perspective_validate_view`, then deploys with `perspective_upsert_view`, which validates
+again, writes the view, and triggers a project scan. A full round-trip example is in
+[examples/deploy-dashboard.md](examples/deploy-dashboard.md).
+
+## Development
+
+```bash
+git clone https://github.com/jsgorana/ignition-mcp
+cd ignition-mcp
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+
+ruff check src tests          # lint
+pytest tests/unit             # unit tests, no gateway needed
+python bridge/build_zip.py    # rebuild the bridge project archive
+
+# Live integration suite (needs a real 8.3 gateway with the bridge installed):
+IGNITION_URL=... IGNITION_API_TOKEN=... IGNITION_BRIDGE_SECRET=... \
+IGNITION_ALLOW_WRITES=true python tests/live/live_check.py
+```
+
+## Acknowledgments
+
+Built on the [Model Context Protocol](https://modelcontextprotocol.io) and its
+[Python SDK](https://github.com/modelcontextprotocol/python-sdk), using
+[httpx](https://www.python-httpx.org/) for HTTP. The
+[ignition-sdk-examples](https://github.com/inductiveautomation/ignition-sdk-examples) repository
+was a useful reference while working out how Ignition's module and scripting APIs fit together.
+
+## License
+
+MIT. See [LICENSE](LICENSE).
+
+## Disclaimer
+
+This project is independent and community-built. It is not affiliated with, endorsed by, or
+sponsored by Inductive Automation. "Ignition" and "Perspective" are trademarks of Inductive
+Automation, LLC, used here only to describe compatibility. Test any write-enabled tool against a
+non-production gateway before pointing it at something that matters.

ignition_mcp-0.1.0/README.md

@@ -0,0 +1,175 @@
+<!-- mcp-name: io.github.jsgorana/ignition-mcp -->
+# ignition-mcp
+
+An MCP (Model Context Protocol) server for Inductive Automation Ignition. It gives an AI
+assistant, Claude Desktop, Claude Code, or any [MCP client](https://modelcontextprotocol.io),
+structured access to an Ignition gateway: browse and write tags, query history and alarms,
+manage projects, and deploy full Perspective views.
+
+Tested against Ignition 8.3. 43 tools spanning tags, history, alarms, projects, gateway
+administration, and Perspective. The server is read-only by default; every write is gated behind
+an explicit opt-in.
+
+```
+You:    "Deploy a Perspective dashboard to a new project called LineOverview with a
+         gauge bound to [default]Line1/Speed."
+Claude: (bootstraps the project, writes the view, wires the tag binding, triggers a scan)
+        -> https://gateway:8088/data/perspective/client/LineOverview
+```
+
+## Why two planes
+
+Ignition 8.3 ships a native REST API, but it doesn't expose live tag values, tag history, alarm
+queries, or Perspective view resources. `ignition-mcp` covers the gap with two transport planes:
+
+- **REST plane.** The gateway's native `/data/api/v1` API, authenticated with an API key, used
+  for projects, gateway configuration, modules, logs, backups, and Perspective session
+  diagnostics.
+- **Bridge plane.** A small WebDev project (`mcp-bridge`) you install once on the gateway. It
+  exposes the gateway scripting surface (`system.tag.*`, `system.alarm.*`, `system.db.*`, and
+  project file I/O) over HMAC-signed HTTP requests.
+
+Tools that need the bridge degrade with a clear message if it isn't installed. Run
+`ignition_diagnose` any time to see what's configured and what's missing.
+
+## Quickstart
+
+### 1. Create an API key on the gateway
+
+Gateway web UI -> Config -> Security -> API Keys -> Create. Give it a name, for example `claude`.
+Copy the full token; it looks like `claude:AbCd...`.
+
+The key's auto-created security level (`Authenticated/<key-name>`) needs to be granted gateway
+read/write access under Config -> Security -> General -> Gateway Read/Write Permissions. Skip
+this step and calls return HTTP 403; `ignition_diagnose` will tell you and give the exact fix.
+
+### 2. Install ignition-mcp
+
+```bash
+pipx install ignition-mcp
+# or: uvx ignition-mcp
+# or: pip install ignition-mcp
+```
+
+### 3. Configure your MCP client
+
+Claude Desktop (`claude_desktop_config.json`) or Claude Code (`.mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "ignition": {
+      "command": "ignition-mcp",
+      "env": {
+        "IGNITION_URL": "http://localhost:8088",
+        "IGNITION_API_TOKEN": "claude:YOUR_SECRET_HERE"
+      }
+    }
+  }
+}
+```
+
+Restart the client and ask it to run `ignition_diagnose`. You should get an all-green checklist,
+aside from a warning about the bridge, which is the next step.
+
+### 4. Install the bridge (recommended, needed for live data and Perspective deploys)
+
+Generate a random secret, enable writes, and let the server install the bridge for you:
+
+```json
+"env": {
+  "IGNITION_URL": "http://localhost:8088",
+  "IGNITION_API_TOKEN": "claude:YOUR_SECRET_HERE",
+  "IGNITION_BRIDGE_SECRET": "a-long-random-string",
+  "IGNITION_ALLOW_WRITES": "true"
+}
+```
+
+Ask your assistant to install the bridge (this runs the `bridge_install` tool), then run
+`ignition_diagnose` again to confirm the bridge check is green. See
+[docs/bridge.md](docs/bridge.md) for the manual install path and troubleshooting.
+
+## Configuration
+
+| Variable | Required | Default | Meaning |
+|---|---|---|---|
+| `IGNITION_URL` | yes | none | Gateway base URL, e.g. `http://localhost:8088` |
+| `IGNITION_API_TOKEN` | yes | none | API key, `name:secret` |
+| `IGNITION_BRIDGE_SECRET` | no | unset | HMAC secret for the bridge; bridge tools are disabled without it |
+| `IGNITION_ALLOW_WRITES` | no | `false` | Master switch for every mutating tool |
+| `IGNITION_TLS_VERIFY` | no | `true` | Set to `false` for self-signed dev gateways |
+| `IGNITION_TIMEOUT_S` | no | `30` | Per-request timeout, in seconds |
+| `IGNITION_TAG_WRITE_ALLOWLIST` | no | unset | Comma-separated glob patterns; tag writes outside them are refused |
+
+## Safety model
+
+- Read-only by default. Mutating tools refuse to run unless `IGNITION_ALLOW_WRITES=true` and the
+  call passes `confirm=true`. Your assistant sets `confirm` after you approve the action.
+- Destructive operations echo the name back. Deleting a project or view requires re-sending its
+  exact name.
+- A tag-write allowlist lets you restrict writable tags to specific path globs.
+- REST mutations carry the API key's identity into Ignition's own audit log; bridge mutations log
+  to the `mcp-bridge` logger. Secrets are never logged or echoed back.
+- The bridge's file endpoints are confined to `data/projects/`; nothing outside that tree is
+  reachable.
+
+## Tool catalog
+
+| Area | Tools |
+|---|---|
+| Diagnostics | `ignition_diagnose`, `gateway_info`, `gateway_trial_status`, `gateway_trial_reset` |
+| Tags | `tag_browse`, `tag_read`, `tag_write`, `tag_create`, `tag_config_export`, `tag_config_import` |
+| History | `history_query`, `history_providers` |
+| Alarms | `alarm_status`, `alarm_journal`, `alarm_acknowledge` |
+| Projects | `project_list`, `project_get`, `project_create`, `project_delete`, `project_export`, `project_import`, `project_scan` |
+| Perspective | `perspective_bootstrap_project`, `perspective_list_views`, `perspective_get_view`, `perspective_upsert_view`, `perspective_delete_view`, `perspective_validate_view`, `perspective_page_config_get/set`, `perspective_session_props_get`, `perspective_style_upsert`, `perspective_list_sessions` |
+| Gateway admin | `gateway_modules`, `gateway_logs_query`, `gateway_logger_set_level`, `gateway_backup`, `gateway_performance`, `config_resource_list` |
+| Database | `db_run_named_query`, `db_query` |
+| Bridge | `bridge_install`, `bridge_status` |
+
+The server also exposes MCP resources the assistant can read to author valid Perspective views:
+`ignition://docs/view-schema` and `ignition://templates/view/{flex-basic,coordinate-basic,tag-bound-dashboard}`.
+
+## Building Perspective views
+
+See [docs/perspective-authoring.md](docs/perspective-authoring.md) for the full writeup. In
+short: the assistant reads the view-schema resource, starts from a template, validates offline
+with `perspective_validate_view`, then deploys with `perspective_upsert_view`, which validates
+again, writes the view, and triggers a project scan. A full round-trip example is in
+[examples/deploy-dashboard.md](examples/deploy-dashboard.md).
+
+## Development
+
+```bash
+git clone https://github.com/jsgorana/ignition-mcp
+cd ignition-mcp
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+
+ruff check src tests          # lint
+pytest tests/unit             # unit tests, no gateway needed
+python bridge/build_zip.py    # rebuild the bridge project archive
+
+# Live integration suite (needs a real 8.3 gateway with the bridge installed):
+IGNITION_URL=... IGNITION_API_TOKEN=... IGNITION_BRIDGE_SECRET=... \
+IGNITION_ALLOW_WRITES=true python tests/live/live_check.py
+```
+
+## Acknowledgments
+
+Built on the [Model Context Protocol](https://modelcontextprotocol.io) and its
+[Python SDK](https://github.com/modelcontextprotocol/python-sdk), using
+[httpx](https://www.python-httpx.org/) for HTTP. The
+[ignition-sdk-examples](https://github.com/inductiveautomation/ignition-sdk-examples) repository
+was a useful reference while working out how Ignition's module and scripting APIs fit together.
+
+## License
+
+MIT. See [LICENSE](LICENSE).
+
+## Disclaimer
+
+This project is independent and community-built. It is not affiliated with, endorsed by, or
+sponsored by Inductive Automation. "Ignition" and "Perspective" are trademarks of Inductive
+Automation, LLC, used here only to describe compatibility. Test any write-enabled tool against a
+non-production gateway before pointing it at something that matters.

ignition_mcp-0.1.0/bridge/build_zip.py

@@ -0,0 +1,76 @@
+#!/usr/bin/env python3
+"""Deterministically build bridge/mcp-bridge.zip — an importable Ignition project
+containing the mcp-bridge WebDev endpoint and its script library.
+
+The BRIDGE_SECRET placeholder stays intact; it is substituted at install time
+(bridge_install tool) or by the operator during a manual import.
+
+Usage: python bridge/build_zip.py
+"""
+
+from __future__ import annotations
+
+import io
+import json
+import zipfile
+from pathlib import Path
+
+HERE = Path(__file__).parent
+SRC = HERE / "src"
+OUT = HERE / "mcp-bridge.zip"
+PERSPECTIVE = "com.inductiveautomation.perspective"
+
+# Fixed timestamp for reproducible archives.
+ZINFO_DATE = (2026, 1, 1, 0, 0, 0)
+
+
+def _write(zf: zipfile.ZipFile, arcname: str, data: str) -> None:
+    info = zipfile.ZipInfo(arcname, date_time=ZINFO_DATE)
+    info.compress_type = zipfile.ZIP_DEFLATED
+    zf.writestr(info, data)
+
+
+def build() -> bytes:
+    lib_code = (SRC / "mcp_bridge_lib.py").read_text()
+    endpoint_code = (SRC / "doPost.py").read_text()
+
+    buf = io.BytesIO()
+    with zipfile.ZipFile(buf, "w") as zf:
+        _write(zf, "project.json", json.dumps({
+            "title": "MCP Bridge",
+            "description": "WebDev bridge for ignition-mcp",
+            "parent": "",
+            "enabled": True,
+            "inheritable": False,
+        }, indent=2))
+
+        # Script library: ignition/script-python/mcp_bridge_lib/code.py
+        lib_dir = "ignition/script-python/mcp_bridge_lib"
+        _write(zf, f"{lib_dir}/code.py", lib_code)
+        _write(zf, f"{lib_dir}/resource.json", json.dumps({
+            "scope": "G", "version": 1, "restricted": False, "overridable": True,
+            "files": ["code.py"], "attributes": {},
+        }, indent=2))
+
+        # WebDev endpoint: com.inductiveautomation.webdev/resources/api
+        api_dir = "com.inductiveautomation.webdev/resources/api"
+        _write(zf, f"{api_dir}/doPost", endpoint_code)
+        _write(zf, f"{api_dir}/config.json", json.dumps({
+            "resource-type": "python-resource",
+            "doPost": {"enabled": True, "require-https": False, "require-auth": False},
+        }, indent=2))
+        _write(zf, f"{api_dir}/resource.json", json.dumps({
+            "scope": "G", "version": 1, "restricted": False, "overridable": True,
+            "files": ["config.json", "doPost"], "attributes": {},
+        }, indent=2))
+
+    return buf.getvalue()
+
+
+def main() -> None:
+    OUT.write_bytes(build())
+    print(f"wrote {OUT} ({OUT.stat().st_size} bytes)")
+
+
+if __name__ == "__main__":
+    main()

ignition_mcp-0.1.0/bridge/src/doPost.py

@@ -0,0 +1,2 @@
+def doPost(request, session):
+	return mcp_bridge_lib.handle(request)