Set up Stackarr from chat

Agent-led setup is the recommended path. Your assistant can inspect the new install, explain the useful choices, prepare a dry-run, and apply the result after you approve it.

The dashboard remains available throughout setup and shows the same saved state.

Connect with setup authority

Install Stackarr first, then generate an admin connection for your MCP client. For Codex:

docker exec app /app/bin/stackarr mcp config codex --profile admin

Run the generated command on the Docker host.

See MCP connections for other clients.

Send this first message

Inspect my new Stackarr install. Recommend safe local defaults, show me a dry-run, and ask before applying changes or interrupting a media service.

The assistant should confirm only choices that materially affect your stack:

• where media, downloads, and backups live
• Plex, Jellyfin, or both
• movies, TV, music, books, photos, or games
• Transmission or qBittorrent
• local-only or intentional remote access
• app-local databases or shared Postgres

Review the plan

Before approving setup, check:

1. the host folders that will be mounted
2. the containers that will be enabled
3. the ports that will be published
4. the backup location and schedule
5. whether any public route will be created

Stackarr asks for approval in the chat client before applying the setup. If that client cannot display MCP approval prompts, the action fails closed.

Move to everyday authority

After setup finishes, change the connection from admin to manage and reconnect. Stackarr will advertise actions only for the apps you selected.

Use unrestricted only when you deliberately want the agent to act without per-action approval prompts. The agent cannot change its own authority profile.