This flow has been demonstrated with Codex CLI and a locally configured MCP server on Windows. Installation details vary by Host. This is not a universal one-click setup.
Prerequisites
You need Python 3.10+, Git, the project source, and a local MCP Host that can run a stdio server. You do not need GitHub write credentials for this conceptual preview path.
Prepare the source checkout
Clone the repository, create an isolated Python environment, then install dependencies from the repository's runtime lock file.
git clone https://github.com/zevsol/delivery-system.git
cd delivery-system
python -m venv .venv
.\.venv\Scripts\python.exe -m pip --isolated install --no-user --no-cache-dir --index-url https://pypi.org/simple --no-require-hashes -r pylock.tomlRequires network access to PyPI. For POSIX systems, use .venv/bin/python.
Configure local stdio MCP
In your Host, configure one MCP server with the repository Python executable and arguments shown below. Set the working directory to the repository root so the source module is importable.
<repo>\.venv\Scripts\python.exe -B -m mcp_server.server --workspace-root <absolute-workspace-path>Choose a dedicated local workspace directory for Preview state. The default profile does not select --host-profile github-app-write. Host configuration syntax is application-specific.
The currently tested default Host still registers other approval/apply tools. "Preview-only" describes this demonstrated workflow, not tool-level enforcement by the Host.
Load the planning Skill
Expose plan-github-work-items from the bundled Skill folder ↗ using your Host's own Skill mechanism. Not all MCP Hosts discover repository Skills automatically; there is no universal install command. Repository sync pending: the copyable-Markdown presentation update was verified in a local working tree, but is not yet merged into the public main. A fresh clone of the current public branch may show only the earlier Preview response until that change is integrated.
Describe the outcome
Supply a development request with a goal, scope, constraints, and things you explicitly don't want. Here is a representative example:
“Build a responsive developer portfolio with an introduction, project showcase, and contact links. It should work on desktop and mobile, use mostly static content, and support keyboard navigation. Do not include login, payments, or an admin panel.”
Inspect the result
A successful call returns a Sealed Preview ID and Revision, plus structured work items. The updated planning Skill can present a GitHub Issue Markdown draft to review and copy.
The local PreviewStore may change. No GitHub Issue is created by this step.
If you have not provided repository claims, do not interpret this as a check against existing remote issues.
Formal audit, human approval, and write execution are not covered by this first-run guide.
Go deeper in the repository
Technical contracts are maintained in the source repository, not duplicated across this marketing site.