Self-hosting.
Deploy Empirical in your own environment while preserving OAuth-protected MCP and API workflows.
Runtime stack
Deploy the server, web app, storage backend, and MCP endpoint in a coordinated environment. This page is for operators running Empirical infrastructure—not for normal CLI users.
Critical config
Set auth mode, storage mode, and public URLs consistently across server and web. Keep OAuth signing material, storage credentials, and public callback URLs in the deployment secret/config system.
MCP_AUTH_MODE=oauth
STORAGE_TYPE=local|firebase|s3
PUBLIC_URL=https://your-domain.example
Validation and limits
Smoke-test OAuth token flow and MCP tool discovery after each deployment, then test one read and one confirmed write. Self-hosting requires maintaining storage, OAuth, backups, and upgrades yourself; it is not a hosted-plan shortcut.
Operational boundary: Use the hosted Empirical endpoint unless you need infrastructure ownership or a private deployment.
Last updated: May 21, 2026