Security
Overview
AutoMD is designed to run in trusted environments. Here are key security considerations for production deployments.
Network access
By default, AutoMD binds to all interfaces (0.0.0.0). For production:
- Place behind a reverse proxy (nginx, Caddy, Traefik)
- Enable HTTPS/TLS termination at the proxy level
- Restrict network access to trusted clients
MCP authentication
When exposing the MCP endpoint, consider:
- Restricting access via network policies
- Using API keys (coming soon)
- Running behind an auth proxy
Warning
Do not expose AutoMD directly to the internet without a reverse proxy and access controls.
Info
Authentication, authorization, and audit logging features coming soon.