Skip to content

Plompy 0.13.0: Local MCP, ready-made Docker images

Latest

Choose a tag to compare

@dalkedev dalkedev released this 12 Nov 16:45
· 1 commit to main since this release
e57c6ab

Plompy Local is ready to pull from GHCR. Connect OpenCode, Codex, Claude Code or another compatible MCP client to tools running in Docker, without building from source. Your agent and model stay in your host client; Local mode does not need Discord.

Start without a source checkout

Download the attached plompy-local-0.13.0.tar.gz, extract it into a new directory, then run:

docker compose pull local
docker compose run --rm -T local node scripts/integrations.mjs init --mode local
docker compose up -d local
docker compose exec -T local node scripts/integrations.mjs test --mode local

Follow the Docker quickstart and the OpenCode, Codex or Claude Code connection guide. The kit contains Compose, security profiles, client configuration examples and a checksum manifest. Its separate .sha256 asset verifies the downloaded archive.

Images

All three variants support Linux amd64 and arm64, including Docker Desktop on Apple Silicon:

Image Use
ghcr.io/dalkedev/plompy-engine:0.13.0-local Local MCP, public page fetching and JSON/CSV artifacts
ghcr.io/dalkedev/plompy-engine:0.13.0-local-browser Local MCP plus sandboxed Chromium for rendered pages
ghcr.io/dalkedev/plompy-engine:0.13.0 Existing Discord engine with its Codex runner

Optional integrations add search, repositories, documentation and analytics. See the integration catalog. Ollama can supply the host agent's model; no model is bundled. Credentials and artifacts persist in separate private volumes. The gateway can save email drafts but does not send email.

The release workflow tests each image on both native architectures before promoting those exact OCI bytes, including provenance and an SBOM. Checks cover authenticated MCP, artifact persistence and the Chromium sandbox. Actual-client acceptance used OpenCode 1.19.5 and Codex with a deterministic local model fixture; live model-provider inference and private vendor accounts were not used as release tests.

Existing Discord installations keep SQLite schema 6 and are not updated automatically. See the changelog and upgrade guidance.