AgentChat — LLM Chat + MCP Integration

Practical Notes

• GitHub: 712 stars · 73 forks; pushed 2026-04-15 (verified via GitHub API).
• docker/README.md lists Docker 20.10+ and Compose 2.0+, plus default ports: UI 8090, API 7860, MySQL 3306, Redis 6379.
• docker/README.md uses a YAML config file (docker_config.yaml) instead of env vars for model keys and DB endpoints.

Main

Operational hardening checklist:

1. Keep secrets out of git: store docker_config.yaml outside the repo or use a templated file + secret manager.
2. Put the API behind an auth layer (reverse proxy + JWT/OAuth) before exposing it to the internet.
3. Separate “chat UI” from “tool execution”: run tools in a constrained worker with clear timeouts and resource limits.
4. Add backups for MySQL and object storage from day one—RAG and chat history are your core assets.

Once stable, you can wire MCP servers as controlled integrations rather than ad-hoc scripts.

FAQ

Q: Is Docker required? A: No, but the repo includes a Docker deployment path that is the quickest way to trial the full stack.

Q: Where do I configure model keys? A: docker/README.md says it uses a YAML config file (docker_config.yaml) rather than env vars.

Q: What should I lock down first? A: Authentication + network exposure; then isolate tool execution and add backups.