poke-pc

<div align="center"> <h1>Poke PC</h1> <p> safely extend poke's capabilities to your machine with an isolated docker environment </p>

<p> </p> </div>

npx poke-pc

or

npx github:calganaygun/poke-pc

A Dockerized MCP worker with persistent terminal control, automatic Poke tunnel connection, and optional webhook notifications.

License: MIT

Use this direct recipe link:

https://poke.com/r/kWWE0sbthIQ

You can also copy RECIPE.md into your Poke configuration.

The command runs an interactive setup that:

• checks Docker
• ensures poke login credentials exist (required for tunnel)
• asks if webhook mode should be enabled
• asks for POKE_API_KEY only if webhook mode is enabled
• creates persistent volume and starts container in detached mode (no --rm)

Useful after setup:

docker logs -f poke-pc
docker exec -it poke-pc tail -f /root/poke-pc/terminal/history.ndjson

• Tunnel auth uses poke login credentials from ~/.config/poke/credentials.json.
• Webhook integration uses POKE_API_KEY.
• Get your API key from https://poke.com/kitchen/api-keys.
• Without API key, webhook notifications are disabled.

If credentials are missing on first run, the app shows a login URL and code in logs.

docker run -d \
  --name poke-pc \
  -p 3000:3000 \
  -e POKE_TUNNEL_NAME="poke-pc" \
  -e MCP_PUBLIC_URL="http://127.0.0.1:3000/mcp" \
  -e POKE_PC_AUTOREGISTER_WEBHOOK="true" \
  -e POKE_API_KEY="${POKE_API_KEY}" \
  -v poke_pc_state:/root/poke-pc \
  -v "$H