Skip to main content
MeepaGateway uses a YAML config file. The default location is ~/.meepagateway/config.yaml. Specify a custom path with --config:
If no config file exists on first run, the gateway enters setup mode.

File format

The config is YAML. Top-level sections:

providers

Per-provider fields (under providers.providers.<name>):

captain

Exposure modes:

cron

Cron jobs are defined per-agent under agents[].cron_jobs. See Cron.

agents

Each item in the agents list defines one agent. All configuration fields are set directly on the agent.
Agent workspace is auto-derived from the ID: ~/.meepagateway/agents/{id}/. Files in the workspace (SOUL.md, MEMORY.md, USER.md, memory.db, skills/, .mcp.json) are not configured here.

file_access

Controls which paths the file tools can read or write.

image_config

Configuration for the sandbox image used in container mode.

container_mode

Runtime settings for the container execution environment.
See Isolation for full details.

Connectors

Connectors are flat objects — all fields are directly on the connector, not nested under a type key.
Set webhook: true on any connector to use the centralized webhook system instead of per-connector polling or WebSocket.

Cron jobs

Tool filtering

allow is an allowlist — only listed tools are available. deny removes specific tools. The two are mutually exclusive.

MCP servers

MCP servers are not configured in the main config file. Each agent has a .mcp.json file at ~/.meepagateway/agents/{id}/.mcp.json:
Edit with: meepagateway agent mcp <id>

Environment variables

Never put secrets directly in the config file. Reference them via api_key_env pointing to an environment variable.

Complete example