+
+
diff --git a/examples/server-deployment/docker/site/site.webmanifest b/examples/server-deployment/docker/site/site.webmanifest
new file mode 100644
index 0000000..fbf43c0
--- /dev/null
+++ b/examples/server-deployment/docker/site/site.webmanifest
@@ -0,0 +1,14 @@
+{
+ "name": "Teradata MCP Server",
+ "short_name": "Teradata MCP",
+ "icons": [
+ {
+ "src": "/favicon.png",
+ "sizes": "192x192",
+ "type": "image/png"
+ }
+ ],
+ "theme_color": "#FF6200",
+ "background_color": "#ffffff",
+ "display": "standalone"
+}
diff --git a/examples/server-deployment/quickstart-docker.md b/examples/server-deployment/quickstart-docker.md
new file mode 100644
index 0000000..505879a
--- /dev/null
+++ b/examples/server-deployment/quickstart-docker.md
@@ -0,0 +1,153 @@
+# Quickstart — Docker Compose (MCP + Caddy HTTPS)
+
+This guide shows how to run the **Teradata MCP server** behind **Caddy** with automatic **HTTPS (Let’s Encrypt)** using **Docker Compose**. It keeps port **8001** private and exposes only **80/443**.
+
+---
+
+## 0) Prerequisites
+
+- Docker + Docker Compose plugin installed.
+- An EC2 instance or host with public IPv4.
+- A DNS record pointing to your host (e.g. `teradata-mcp.duckdns.org → `).
+ *(you can use a free dynamic DNS service such as DuckDNS for testing...)*
+- Security Group / firewall allows inbound **TCP 80** and **TCP 443** (keep **22** for SSH).
+
+---
+
+## 1) Folder layout
+
+Copy the [docker](examples/server-deployment/docker) directory outside this code directory and move into it this is the structure:
+
+```
+examples/server-deployment/docker/
+├─ docker-compose.yml
+├─ .env
+├─ Dockerfile
+├─ deploy/
+│ └─ caddy/
+│ └─ Caddyfile
+└─ site/
+ ├─ favicon.ico # optional
+ ├─ favicon.png # optional
+ └─ index.html # optional landing page
+```
+
+Eg.
+```bash
+#If you haven't, clone this repo
+git clone https://github.com//teradata-mcp-server.git
+
+cp -R teradata-mcp-server/examples/server-deployment/docker teradata-mcp-service
+cp teradata-mcp-server/Dockerfile teradata-mcp-service
+cd teradata-mcp-service
+```
+
+
+---
+
+## 2) `.env` — runtime configuration
+
+Update the `.env` file with your database connection string for `DATABASE_URI` and domain name for `DOMAIN`:
+
+```dotenv
+# --- MCP server (FastMCP) ---
+DATABASE_URI=teradata://USER:PASS@HOST:1025/DEFAULT_DB_SCHEMA # <-- Update here
+MCP_TRANSPORT=streamable-http
+MCP_HOST=0.0.0.0
+MCP_PORT=8001
+
+# --- Caddy / HTTPS ---
+# Set this to the DNS name that points at your server
+DOMAIN=teradata-mcp.duckdns.org # <-- Update here
+```
+
+> Keep secrets out of command history by using `.env`. For all supported vars, see **docs/server_guide/CONFIGURATION.md**.
+
+---
+
+## 3) (Optional) landing page / favicon
+
+Add files under `examples/server-deployment/docker/site/` if you want a root page or custom icon:
+
+- Update `favicon.ico` and `favicon.png` with your preferred icon
+- Update `index.html` (minimal example)
+
+---
+
+## 4) Start the stack
+
+From your directory:
+
+```bash
+docker compose up -d --build
+docker compose ps
+```
+
+First-time HTTPS may take ~30–90 seconds. Watch Caddy:
+
+```bash
+docker compose logs -f caddy
+```
+
+---
+
+## 7) Verify
+
+```bash
+# Expect 200/401/405 from the app (not HTML)
+curl -i https://${DOMAIN}/mcp/
+
+# Inside the network (debug): curl from caddy to mcp
+docker compose exec caddy sh -lc 'wget -qO- http://mcp:8001/mcp/ | head'
+```
+
+If you added a landing page: visit `https://${DOMAIN}/`.
+
+---
+
+## 8) Use with Claude Desktop
+
+With HTTPS you **do not** need `--allow-http`:
+
+```json
+{
+ "mcpServers": {
+ "teradata_mcp_remote_https": {
+ "command": "npx",
+ "args": ["mcp-remote", "https://YOUR_DOMAIN/mcp/"]
+ }
+ }
+}
+```
+
+Add headers if you enforce auth at the app or proxy (e.g., `--header "Authorization: Basic ${AUTH_TOKEN}"`).
+
+---
+
+## 9) Operations
+
+```bash
+# Update/recreate
+docker compose pull && docker compose up -d --build
+
+# Logs
+docker compose logs -f mcp
+docker compose logs -f caddy
+
+# Stop
+docker compose down
+```
+
+---
+
+## 10) Troubleshooting
+
+- **TLS errors right after deploy** → DNS propagation or first ACME run; retry in a minute and check `docker compose logs -f caddy`.
+- **HTML/404 served at `/mcp/`** → ensure the `@mcp` matcher appears *before* the static handlers in `Caddyfile`.
+- **80/443 blocked** → open in Security Group / firewall; confirm public IPv4 resolves for `${DOMAIN}`.
+- **Icon still shows DuckDNS duck** → Claude may brand by base domain (`duckdns.org`). Use your own domain to fully customize.
+
+---
+
+**That’s it.** You now have a clean, HTTPS-protected MCP server via Docker Compose with Caddy.
+-----
+