Use of the eGrow MCP server is governed by the eGrow Terms of Service. The following terms apply specifically to MCP access.
graphql_query and graphql_mutation escape hatches are audited; misuse (e.g., bulk export, schema scraping) is a breach of these terms.Best-effort availability. The MCP server is operationally tied to the eGrow API — if the eGrow API is unavailable, the MCP server returns UPSTREAM_UNAVAILABLE errors with retry_safe: true.
We may add, change, or remove tools without notice as the eGrow API evolves. Breaking changes will be communicated through the eGrow changelog.