Skip to content

Plompy 0.13.1: Configurable Local MCP port

Latest

Choose a tag to compare

@dalkedev dalkedev released this 18 Nov 18:51
· 10 commits to main since this release

Plompy Local 0.13.1 lets you choose the host port without changing the gateway's internal port. Docker keeps the gateway on IPv4 loopback. Client configuration exports use the chosen port.

Download and extract plompy-local-0.13.1.tar.gz into a private directory. Check it against the attached SHA-256 file and follow the Docker quickstart. The default endpoint is http://127.0.0.1:7331/mcp. To use an alternate port, add PLOMPY_LOCAL_HOST_PORT=17331 to the Compose project's .env before startup.

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

When upgrading, keep the same Compose project name to reuse your existing config, token and artifacts. Follow the upgrade guide before replacing the kit files.

The stable Discord engine keeps its Codex runner and SQLite schema 6. The personal assistant remains an opt-in prerelease.

Container images

The release workflow tested and published each variant for Linux amd64 and arm64.

  • Discord engine ghcr.io/dalkedev/plompy-engine:0.13.1

    • ghcr.io/dalkedev/plompy-engine@sha256:813babe2cd3a8e9ffcda9d8a4df547725980a5eecc0ff08fd3f517fda25770e5
  • Local MCP ghcr.io/dalkedev/plompy-engine:0.13.1-local

    • ghcr.io/dalkedev/plompy-engine@sha256:0871e5e187b44c684b9c4ddf95fa34cf742f4e5ea8e25819035902b891134f57
  • Local MCP with sandboxed Chromium ghcr.io/dalkedev/plompy-engine:0.13.1-local-browser

    • ghcr.io/dalkedev/plompy-engine@sha256:910a350242fed696c89e08dc914e6002e47cd43bf645a5e3f13114417e0be51c

Release workflow