Aviato / docs
Reference

Connector configuration

Environment variables used by the database connector.

View Markdown

These settings configure the connector process. They are separate from the API server's environment variables.

VariableDefault / requirementPurpose
AVIATO_CONTROL_PLANE_URLRequiredAbsolute HTTP(S) control-plane URL.
AVIATO_CONNECTOR_TOKENRequiredDeployment credential issued for the environment.
AVIATO_DATABASE_URLRequiredMain datasource connection string.
AVIATO_PUBLIC_URLhttp://localhost:8080 with the configured portURL browsers and MCP clients use to reach the connector. Set HTTPS in production.
PORT8080Connector listening port.
AVIATO_DATA_DIR./.aviatoPersistent local state directory; mount durable storage.
AVIATO_DB_SCHEMApublic for PostgreSQLSchema to expose.
AVIATO_MONGO_SAMPLE_SIZE1000Documents sampled per collection for field inference.
AVIATO_DATASOURCE_<NAME>_URLOptionalAdditional datasource; names are lowercased. main and plugin are reserved.
AVIATO_DATASOURCE_<NAME>_SCHEMApublic for PostgreSQLSchema for an additional datasource.
AVIATO_PLUGIN_URLOptionalSDK plugin base URL. Requires its matching secret.
AVIATO_PLUGIN_SECRETOptionalSignature secret shared with the plugin. Requires its URL.
AVIATO_DECISIONS_URLOptionalSelf-hosted decision service URL.
AVIATO_UPLOADS_BUCKETOptionalEnables uploads to your S3-compatible bucket.
AVIATO_UPLOADS_PREFIXaviato/Object-key prefix for uploads.
AVIATO_UPLOADS_PUBLIC_URLOptionalPublic base URL stored for uploaded files.
AVIATO_UPLOADS_MAX_SIZE_MB25Per-file size limit.

Database connection schemes

Supported connection forms include PostgreSQL (postgres:// or postgresql://), MySQL (mysql://), MongoDB (mongodb:// or mongodb+srv://), SQLite (file:), and libSQL (libsql://). MongoDB URLs must include a database name.

Use database privileges to restrict the connector independently of application roles. Protect connection strings and tokens as secrets.

The implementation of this reference is runtime/config.ts.

Upgrading from the agent name

The customer-side runtime is now Aviato Connector. AI agents remain MCP clients of the connector.

  • Deploy the updated control plane before upgrading connectors or the dashboard. New connectors call /connector/v1; the control plane also accepts /agent/v1 for existing binaries.
  • Use AVIATO_CONNECTOR_TOKEN. AVIATO_AGENT_TOKEN remains accepted; a nonblank new variable takes precedence.
  • Use CONNECTOR_HOSTING and CONNECTOR_IMAGE on the control plane. Their AGENT_ aliases remain accepted. NOTES_CONNECTOR_PRIVATE_ORIGINS replaces NOTES_AGENT_PRIVATE_ORIGINS with the same fallback.
  • Use aviato-connector and aviato/connector. Release packaging retains the old binary asset names, executable path in Docker, and image tags. These aliases become available only when a connector release is published; this source change does not publish binaries or images.
  • Laravel accepts existing aviato.agent configuration and AVIATO_AGENT_* variables. Existing published configuration takes precedence over package defaults; move that section to aviato.connector when updating it. --agent-version remains an alias for --connector-version. Go retains cmd/aviato-agent-install alongside cmd/aviato-connector-install.
  • Existing database tables, Docker container and volume identities, JWT audiences, protobuf wire fields and agent.status events retain their original names. No data migration or credential rotation is required.
  • Dashboard GraphQL fields use connectorSession, connectorStatus, connectorUrl, connectorConnectedAt, connectorCredential, hostedConnectorsAvailable and rotateConnectorCredential. The old fields remain as deprecated aliases. Existing AgentSession and AgentStatus fragment type names remain compatible.

Keep the connector's data directory when replacing its process or container. It holds queued audit events and local state. Public binary availability still needs separate release verification; use a supplied binary or build from source until it is verified.

Edit on GitHub

On this page