docker-guide

Limitations & Support

• Environment: Self-hosted Docker only. Not supported on AnythingLLM Cloud.
• Protocol Support: Tools only. Resources, Prompts, and Sampling are not supported.

Host Filesystem Access

• Access host files via the container path: /app/server/storage/... (maps to host STORAGE_LOCATION).

Container Environment

• Base OS: ubuntu:jammy-20240627.1
• Pre-installed Binaries: npx, uv, uvx, node, bash

Configuration File

• Path: <STORAGE_LOCATION>/plugins/anythingllm_mcp_servers.json
• Generation: Automatically created upon first access of the “Agent Skills” UI page.

Lifecyle & Operations

Startup Behavior

• MCP servers do not start on container boot.
• Servers auto-start when visiting the “Agent Skills” page or invoking the @agent directive.
• To prevent auto-start, set "anythingllm.autoStart": false in the configuration file.

Adding a Server

Add the configuration object to the mcpServers block in anythingllm_mcp_servers.json.

Removing a Server

• UI: “Agent Skills” -> Select Server -> Gear Icon -> “Delete”.
• Manual: Remove the server object from anythingllm_mcp_servers.json and click “Refresh” in the UI.

Reloading & Restarting

• Hot Reload: Click “Refresh” in the “Agent Skills” page to apply configuration changes without restarting the Docker container.
• Manual Start/Stop: UI -> “Agent Skills” -> Select Server -> Gear Icon -> “Start” / “Stop”.

Troubleshooting & Package Management

Manual Dependency Installation

Run commands inside the running container to install missing tools:

docker exec -it <container_name> uv tool install <package_name>

Note: Manually installed tools and cached libraries do not persist if the container is destroyed/recreated.

Debugging Logs

Monitor container logs for execution errors:

docker logs -f <container_name>