
Renforge
io.github.alex-jordan547Published by GitHub account alex-jordan547v0.7.3Updated Nov 4, 2026
Inspect, drive and debug a running Ren'Py game: state, screenshots, guarded clicks, saves, builds.
Overview
MCP server, CLI and dashboard for Ren'Py visual-novel projects: inspect a project, launch and drive a running game, capture screenshots and build releases.
- What you can do
- Inspect a Ren'Py project: summarize structure, scan scripts, labels and assets, parse lint output
- Launch and drive a running game: advance dialogue, pick choices, evaluate expressions, get/set store variables, send text/key/scroll input, poll events, capture frames
- Read the frame as a structured scene tree with bounds, z-order and style, and measure alignment, spacing, overlap and contrast
- Edit on-screen controls in the Live Editor with source-safe preview and Save, plus autopilot replays with label coverage
- Audit assets and translations: find orphaned or missing files, list languages, generate translation files, export dialogue
- Run desktop and web builds, and search Ren'Py's offline…
- When to use it
- Useful when an assistant works on a Ren'Py visual novel: exploring an unfamiliar project, debugging layout or runtime behaviour, checking scene placement numerically, or automating playthroughs and translation work. It is aimed at local desktop development rather than headless or web use.
- Requirements
- Runs locally over stdio via uvx (Python 3.11+ and uv). Ren'Py itself need not be installed: RenForge reuses an SDK found on the machine or downloads one on first launch. Every tool call takes a project_path argument. The optional dashboard installs extra dependencies.
Installation
In SourceWeft
- Open Renforge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
RenForge
[PyPI] [Python] [License: MIT] [CI]
RenForge is an MCP (Model Context Protocol) server, CLI, and web dashboard for working with Ren'Py visual-novel projects.
It lets an AI agent — or a human via the dashboard — inspect a project, launch
a game with the Live Editor enabled by default, select and inspect on-screen
controls, preview layout changes before writing guarded .rpy source, drive
runtime state, capture screenshots, generate translations, find orphaned
assets, run builds, and search Ren'Py's docs.
[RenForge Live Editor — selected editable control with scene tree, handles, inspector, and style panel]Status: alpha, actively developed. The core surfaces (MCP tools, in-game bridge, Live Editor, CLI, dashboard) are functional; APIs may still change.
Live Editor — select an editable control, inspect it, preview moves, then Save to source
Quick start — dashboard
Requires Python 3.11+ and uv — nothing else. You don't even need Ren'Py installed: RenForge reuses an SDK it finds on your machine, or downloads one automatically on first launch.
Then choose your game in the dashboard's project picker — no path to type. (Or
skip the picker with --project /path/to/your/game.) Launch the game and click
the floating RF control to open the Live Editor.
Live Editor
The Live Editor is the headline 0.7 feature: edit eligible on-screen controls inside the running game, preview layout changes at runtime, and Save only when a target is source-safe. Locked or unsupported targets stay inspectable with a clear reason — they are not silently forced.
Full human and agent workflows, source-safety rules, and screenshots: docs/LIVE_EDITOR.md.
Install
uvx needs no install at all. For a persistent renforge command on your
PATH, use pipx:
[ui] pulls in the optional dashboard stack (Starlette, uvicorn, watchfiles).
Skip it if you only need the MCP server or CLI.
On managed systems (Debian/Ubuntu), plain pip install is blocked by
PEP 668 — use uvx or pipx instead.
Update
What's new: CHANGELOG.md · GitHub releases.
Set up the MCP server (AI agents)
The server command is the same for every client:
Every RenForge tool takes a project_path argument, so the agent passes your
game's path on each call — copy the configs below as-is, no path substitution.
Claude Code
Codex CLI
Claude Desktop, Cursor, Windsurf, Cline, Gemini CLI — same mcpServers
JSON shape in each client's config file:
VS Code (Copilot), Zed, Windows PATH issues, and the pipx variant are covered in the MCP guide.
Verify it works — ask the agent:
Inspect my Ren'Py project at /path/to/game
The agent should call renforge_inspect_project with that path and return a
JSON summary of the project (labels, scripts, assets, and related metadata).
What it does
- Live Editor (default on launch) — in-game selection, inspection, and source-safe preview/Save for editable controls; locked targets stay inspectable. Guide: docs/LIVE_EDITOR.md.
- Project inspection — summarize structure, scan scripts/labels/assets, parse lint output.
- Live game control — launch a project with an injected in-game bridge and Live Editor, then advance dialogue, list/select choices, evaluate expressions, get/set store variables, send focused text/key/scroll input, poll pushed events, and capture frames the model can literally see.
- Scene perception (pixel-perfect, no vision needed) — read the whole frame
as structured logical-coordinate nodes (
renforge_scene_tree): every sprite, control, and text block with bounds, z-order, colour, and style, plus an ASCII wireframe and structural scene diffs. Thenrenforge_measurereports alignment, spacing, overlap, fit, and WCAG contrast as numbers an agent can act on. - Autopilot — auto-play choices backed by Ren'Py menu
itemsacross fresh replays, including custom-named and one-item menus, while reporting label coverage and crashes. Customcall_screeninteractions that do not expose Ren'Py menuitemsare not currently explored automatically. - Assets & translations — find orphaned/missing image+audio assets, list
languages, compute translation stats, generate/update
game/tl/<lang>/files, export dialogue as text. - Builds — package desktop distributions and web builds.
- Docs — search and read Ren'Py's offline documentation.
- Web dashboard — live story map, activity log, autopilot coverage, lint
view, and game-state controls (default
127.0.0.1:8765).
CLI
Documentation
- Live Editor — human and agent workflows, editable vs locked targets, source-safety, public screenshots.
- MCP guide — full tool catalogue, agent workflows (Live Editor, hot reload, saves, pixel-perfect placement, scene perception).
- Runtime policy — operation-level risk enforcement vs MCP
ToolAnnotations, authorization, and the compatibility plan. - Architecture — code layout, live-control flow, Ren'Py SDK resolution, packaging.
- Contributing — dev setup, frontend build, PRs.
- Cloud / CI environment — Cursor Cloud Agents, Xvfb, Ren'Py SDK bootstrap, and env smoke.
- Changelog — release history.
examples/demo_game/— small sample Ren'Py project to try everything on.
License
MIT
Contributors
Special thanks to the people who have contributed to RenForge:
- @AxelBeary — complete Simplified Chinese dashboard translation and related internationalization fixes.
Source: README.md at commit 3fb9031
Tools
0Version history
2- v0.7.3LatestOct 7, 2026
- v0.7.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts