Zola

Host a copy with our keys and logs.

• ZOLA_REFRESH_TOKEN — Zola refresh token JWT (~1 year lifetime). Optional — when unset, the MCP falls back to the ContextMint Bridge browser extension to read the `usr` cookie from your signed-in zola.com tab, and caches it so later starts need no browser.
• ZOLA_DISABLE_FETCHPROXY — Set to '1' to opt out of the fetchproxy browser fallback (headless / CI). With it set and no ZOLA_REFRESH_TOKEN, auth is a hard error unless a previous bootstrap already cached a token — reading that file is not opening a browser, so the cache stays readable.
• ZOLA_TOKEN_CACHE — Set to 'false' to disable the on-disk refresh-token cache and ask the browser on every start. Defaults to enabled. Inert when ZOLA_REFRESH_TOKEN is set — there is no bootstrap to skip.
• ZOLA_TOKEN_FILE — Absolute path for the refresh-token cache file. Defaults to $MCP_DATA_DIR/.zola-mcp/refresh-token.json, else the same path under $HOME.
• ZOLA_ACCOUNT_ID — Overrides the account id normally read from GET /v3/users/me/context. Set it only to pin a specific account.
• ZOLA_REGISTRY_ID — Overrides the registry id normally read from the same context call.
• ZOLA_WEDDING_ID — Overrides the wedding id normally read from the same context call.
• ZOLA_SESSION_TOKEN — A seed session token (JWT). The client refreshes it about five minutes before its exp, so this is a starting point rather than a long-lived credential.
• FETCHPROXY_WS_PORT — Localhost port of the fetchproxy concentrator the ContextMint Bridge extension connects to (default 37149). Every MCP on one machine shares it, so move it for all of them or not at all.
• FETCHPROXY_WS_HOST — Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
• FETCHPROXY_IDENTITY_DIR — Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).