-
Notifications
You must be signed in to change notification settings - Fork 0
Installation Docker
The recommended way to run FICSIT Foreman. Docker Compose brings up the web
app, its backend, and the unified MCP server as one foreman project.
Prefer to run without Docker Desktop, on Windows 11? See Installation — WSL Containers (preview).
From a clone of the repository (for its compose.yaml):
docker compose up -d # pulls the images the first timeThis starts three services:
| Service | Port | What |
|---|---|---|
ff-client (web app) |
8725 | the foreman UI — open http://localhost:8725
|
ff-server (backend) |
8724 | LLM proxy, sessions, work orders, MCP gateway |
sf-mcp (MCP server) |
8723 | game-data + live save-game tools (/health, /mcp) |
It serves the bundled stable game data out of the box. To chat with the foreman you need an LLM API key — see Anthropic or OpenAI.
docker compose pull && docker compose up -d # update to newer images
docker compose stop # turn OFF but keep the containers
docker compose start # turn them back on
docker compose down # remove containers + network (data survives)Your data lives in the foreman-db and foreman-saves volumes and survives stop,
start, and plain down. Only docker compose down -v (or deleting the volumes)
removes it.
If you only want the MCP tools for your own AI client, run the server image on its own:
docker run -d --name foreman-sf-mcp -p 8723:8723 ghcr.io/stuartmeeks/foreman-sf-mcp:latestIt serves the bundled stable data on http://localhost:8723 (health check:
http://localhost:8723/health), then connect a client.
The full Docker / Windows walkthrough — and the from-source (Node.js) path — are in the repository README.
FICSIT Foreman
- Home
- Installation
- API keys
- Configuration
- Game data channels
- Troubleshooting
- MCP clients