Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
TypeScript
services:
mcp-host:
# Build context is the repo root: mcp-host/Dockerfile COPYs the shared
# packages/ it links via file: dependencies.
build:
context: .
dockerfile: mcp-host/Dockerfile
environment:
CLERUM_DEV_MODE: 'true'
CLERUM_ENABLE_AUTH: 'false'
CLERUM_MODEL_PROVIDER: ${CLERUM_MODEL_PROVIDER:-openai}
OPENAI_API_KEY: ${OPENAI_API_KEY:-}
CLAUDE_API_KEY: ${CLAUDE_API_KEY:-}
ZAI_API_KEY: ${ZAI_API_KEY:-}
BAILIAN_API_KEY: ${BAILIAN_API_KEY:-}
# Dev mode runs with auth off and trusts the edge headers, so publish the
# port on loopback only. Never expose it on a reachable interface.
ports:
- '127.0.0.1:8080:8080'
healthcheck:
# Follows CLERUM_SERVER_PORT if it is overridden inside the container.
test:
['CMD-SHELL', 'wget -qO- "http://localhost:$${CLERUM_SERVER_PORT:-8080}/v1/runtime/health"']
interval: 10s
timeout: 5s
retries: 5
start_period: 20s
# channel-reader wires Telegram (or Slack/Email) to mcp-host.
# It requires a real bot token. Omit / comment out this service
# if you only want the local HTTP surface (curl to mcp-host:8080).
channel-reader:
build:
context: ./channel-reader
dockerfile: Dockerfile
depends_on:
mcp-host:
condition: service_healthy
environment:
CLERUM_DEV_MODE: 'true'
CLERUM_HOST_REF: dev-host
CLERUM_MCP_HOST_URL: http://mcp-host:8080
# Replace telegram channel/user IDs to match your bot setup.
# "userIds" is the list of Telegram user IDs allowed to send messages.
CLERUM_CHANNEL: >-
{"hostRef":"dev-host","telegram":[{"channelId":"dev-channel","userIds":["${TELEGRAM_ALLOWED_USER_ID:-123456789}"]}]}
CLERUM_TELEGRAM_BOT_TOKEN: ${CLERUM_TELEGRAM_BOT_TOKEN:-}
profiles:
- telegram