AGENT CONTEXT / DOCS

Run it on your terms.

Understand credentials, storage, backups, and the instance trust boundary.

Connecting teammates? Use the Wi-Fi/LAN, VPN, SSH, and HTTPS setup guide.

Public website and running MCP server

The Vercel website serves documentation and downloads. Run the MCP service on your computer or persistent infrastructure; choose a reachable LAN, private VPN, SSH-tunnel, or HTTPS endpoint for agents on other machines. See shared context across systems.

One instance, one trust boundary

Every token holder can read and write every project in the instance. Agent IDs are self-reported. Run separate instances for unrelated users or teams.

Choose a durable data path

TERMINAL
agent-context-mcp --db /srv/agent-context/context.sqlite3 --token-file /path/to/token

Set AGENT_CONTEXT_DB as an alternative. New installations default to the OS user data directory, outside the npm installation. Keep SQLite on a local durable disk.

Remote access

Use HTTPS through a reverse proxy, keep the application port private, and configure exact Host and Origin allowlists:

TERMINAL
agent-context-mcp --allowed-host context.example.com --allowed-origin https://context.example.com --db /srv/agent-context/context.sqlite3 --token-file /path/to/token

Authentication uses a pre-provisioned bearer token. This release does not provide interactive OAuth login or tenant permissions.

Health and request limits

/healthz reports process liveness. Authenticated /readyz checks database readability. The defaults are a 256 KiB body cap, 600 protected requests per minute, and 32 protected concurrent requests. Use --help for configuration options.

Back up before an upgrade

TERMINAL
agent-context-mcp backup --db /path/to/context.sqlite3 --output /path/to/new-backup.sqlite3
agent-context-mcp check --db /path/to/new-backup.sqlite3

Backups include committed WAL records and refuse to overwrite files. Test restores. Stop all clients before replacing a database, and preserve its original WAL sidecars separately.

Containers

The source includes Docker Compose and a multi-stage Node image with a non-root user, a read-only filesystem, and a persistent volume. Build from source and configure the instance token before exposing the service.