@yoryoboy/bi-mcp 1.17.0 → 1.19.0

package/README.md

@@ -65,6 +65,7 @@ Si no vas a usar una integracion, sus credenciales pueden no ser necesarias para
 El servidor lee infraestructura y secretos desde variables de entorno:
 
 - `MCP_TRANSPORT`, `PORT`, `MCP_URL`
+- `MCP_TOOL_TOTAL_DEADLINE_MS` (optional positive integer; default `300000` milliseconds for each MCP `tools/call`)
 - `DATABASE_URL`, `DB_ENCRYPTION_KEY`
 - `GOOGLE_OAUTH_CLIENT_ID`, `GOOGLE_OAUTH_CLIENT_SECRET`
 - `GA4_PROPERTY_ID`
@@ -73,6 +74,17 @@ El servidor lee infraestructura y secretos desde variables de entorno:
 
 La configuracion de negocio no deberia vivir en `.env`.
 
+The server enforces a five-minute total tool-call boundary at the MCP middleware
+layer (configurable with `MCP_TOOL_TOTAL_DEADLINE_MS`). The outer middleware returns
+a stable privacy-safe timeout error at that deadline and aborts cooperative Mercado
+Libre and VTEX Axios requests. Mercado Libre Axios requests have a 90-second
+timeout; VTEX Axios requests have a 30-second timeout. Buyer reconciliation uses a
+bounded safety margin derived from the global timeout so it can return structured
+per-reference degradation before the outer response wins. Fetch-based provider
+clients, token-refresh fetches, database calls, CPU-bound work, and external SDK
+calls that do not consume the shared signal are explicitly non-cooperative and may
+continue after the caller-visible timeout.
+
 ## Documentacion util
 
 - [Capacidades del MCP](/home/yoryo/apps/bi-mcp-dashboard/docs/content/CAPACIDADES_MCP.md): que puede responder cada modulo.