← Index

io.github.chrischall/zola-mcp

io.github.chrischall/zola-mcpv2.2.2Other

Zola wedding planning for Claude — vendors, budget, guests, seating, registry, and RSVPs

The current version, v2.2.2, was published to the official MCP registry on 2026-11-07. It is distributed as zola-mcp on npm, filed under Other by this index, and declares 11 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using io.github.chrischall/zola-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-28 17:36 UTC
screened 2026-10-05tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No hidden instructions”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-11-21).

Contracts can change after screening, with no version bump. The gate pins io.github.chrischall/zola-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for io.github.chrischall/zola-mcp](https://mcpindex.ai/server/io-github-chrischall-zola-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-chrischall-zola-mcp">Independent trust record for io.github.chrischall/zola-mcp</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-chrischall-zola-mcp)](https://mcpindex.ai/server/io-github-chrischall-zola-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-chrischall-zola-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-chrischall-zola-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
ZOLA_REFRESH_TOKEN
secret

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
secret

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/).

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
10
installability
25
documentation
15
stability
10
Alternatives in Other