Reference deployment for the authenticated HTTP MCP server
The authenticated HTTP MCP transport landed in #36 (foley.make_http_app / foley.serve_http
/ foley-mcp --http --token …, bearer-token, fail-closed). What's missing is a reference
deployment so an operator can actually stand it up.
Scope
- A
Dockerfile (+ compose) that serves foley-mcp --http with the retrieval extras, a
mounted library volume, and tokens via env/secret.
- A short "Deploy the MCP server" doc: TLS termination (behind a reverse proxy — the app is
plain ASGI), token rotation, the --offline posture for sensitive narration, and health/
readiness notes.
- Optional: a rate-limit / concurrency note and a
/healthz route.
Acceptance
docker run … foley-mcp --http --token … serves the tools; an MCP client connects with the
bearer token and a request without it gets a 401.
- The deploy recipe is documented and linked from the README "For AI agents" section.
Refs #36.
Reference deployment for the authenticated HTTP MCP server
The authenticated HTTP MCP transport landed in #36 (
foley.make_http_app/foley.serve_http/
foley-mcp --http --token …, bearer-token, fail-closed). What's missing is a referencedeployment so an operator can actually stand it up.
Scope
Dockerfile(+ compose) that servesfoley-mcp --httpwith the retrieval extras, amounted library volume, and tokens via env/secret.
plain ASGI), token rotation, the
--offlineposture for sensitive narration, and health/readiness notes.
/healthzroute.Acceptance
docker run … foley-mcp --http --token …serves the tools; an MCP client connects with thebearer token and a request without it gets a 401.
Refs #36.