Install guide

Install Pamie with Homebrew or Docker

Pamie can run as a local binary for development or as a Docker container with persistent storage. Both paths bind to localhost by default and require Bearer token configuration for the MCP endpoint.

Homebrew Docker Quickstart

Install the binary with Homebrew

brew install kurocho/tap/pamie
pamie --version

Then create a reusable local token file and run Pamie:

if [ ! -f .pamie.env ]; then
  umask 077
  printf "PAMIE_TOKEN=%s\nPAMIE_TOKEN_ID=local\nPAMIE_TOKEN_SCOPES=all\n" \
    "$(openssl rand -hex 32)" > .pamie.env
fi

set -a
. ./.pamie.env
set +a
printf "MCP endpoint: http://127.0.0.1:8080/mcp\nBearer token: %s\n" "$PAMIE_TOKEN"

pamie \
  --addr 127.0.0.1:8080 \
  --data-dir ./data

Keep `.pamie.env` local and out of version control. Use a service manager or secret store for production deployments.

Run the latest Docker image

docker volume create pamie-data

if [ ! -f .pamie.env ]; then
  umask 077
  printf "PAMIE_TOKEN=%s\nPAMIE_TOKEN_ID=local\nPAMIE_TOKEN_SCOPES=all\n" \
    "$(openssl rand -hex 32)" > .pamie.env
fi

set -a
. ./.pamie.env
set +a
printf "MCP endpoint: http://127.0.0.1:8080/mcp\nBearer token: %s\n" "$PAMIE_TOKEN"

docker run --rm \
  --name pamie \
  -p 127.0.0.1:8080:8080 \
  -v pamie-data:/data \
  --env-file .pamie.env \
  kurocho/pamie:latest

Verify the server

curl http://127.0.0.1:8080/health
curl http://127.0.0.1:8080/ready

Do not expose Pamie publicly without HTTPS termination and Bearer authentication. Keep memories free of secrets unless your deployment model and retention policy are designed for that data.

View source Docker Hub