waro-mcp
This server exposes Waro Colombia's commercial APIs via MCP, enabling agents to inspect sales, customers, menu, analytics, loyalty (WAROS), and run safe queries.
Core:
waro_pinghealth check;waro_schemaintrospects available contracts/tools.Sales: list orders with filters (status, date, payment, sort), aggregated metrics by date/product/payment/ticket, and full order detail by UUID.
Customers: list customers with frequency/value/balance, customer details/history, per-customer orders, and new-vs-recurring metrics.
Menu: browse products, active recipes, and modifier groups.
Analytics: menu performance, food cost/margin, analytical alerts, data-quality warnings, cohort retention, WAROS issued/redeemed analytics, RFM segmentation, and churn-risk customers.
Financial: product-level margin, cost, and profit analysis.
WAROS loyalty: estimate WAROS for a purchase, query balances for multiple profiles, and get a customer's WAROS summary.
Queries: list QuerySpec datasets/dimensions/measures and safely run analytics queries.
Operations: returns
waro.agent.v1envelopes, supports stdio and remote HTTP with per-requestwaro_sk(multitenant) or env-based legacy auth.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@waro-mcp show me today's sales metrics"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
waro-mcp
MCP server for Waro Colombia — replacement for waro-cli for LLMs/agents. Reuses Waro API endpoints (api-warolabs/api-warocol.com) and contracts (contract.rs).
Install
npm install
npm run buildRelated MCP server: whatsapp-mcp-server
Run (stdio)
node build/index.js
# or
npm startInspector
npx @modelcontextprotocol/inspector node build/index.jsRun (HTTP — remote for LLMs, multitenant)
# Per-request: el cliente manda su waro_sk, no necesitas WARO_API_KEY en env
MCP_PORT=8090 MCP_PATH=/mcp node build/http.js
# health (sin auth)
curl http://127.0.0.1:8090/health
# MCP con tenant del cliente
curl -H "Authorization: Bearer waro_sk_TU_KEY" -H "Accept: application/json, text/event-stream" -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' \
http://127.0.0.1:8090/mcp
# Fallback legacy single-tenant (si no mandas waro_sk, usa env)
WARO_API_KEY=waro_sk_xxx MCP_PORT=8090 node build/http.jsDocker (hostinger — sin MCP_AUTH_TOKEN requerido):
docker compose up -d --build
# nginx: deploy/nginx-mcp.conf -> mcp.warolabs.com -> 127.0.0.1:8090 (CloudFront + origin-guard)
# Opcional legacy: MCP_AUTH_TOKEN=secret solo si quieres auth extra además de waro_skMCP config (OpenCode / Claude Desktop)
Stdio (local):
{
"mcpServers": {
"waro-mcp": {
"command": "node",
"args": ["/ABSOLUTE/PATH/waro-mcp/build/index.js"],
"env": { "WARO_API_KEY": "waro_sk_xxx", "WARO_API_URL": "https://api.warolabs.com" }
}
}
}Remote (HTTP — multitenant, el cliente usa su propia waro_sk):
{
"mcpServers": {
"waro-mcp": {
"type": "http",
"url": "https://mcp.warolabs.com/mcp",
"headers": { "Authorization": "Bearer waro_sk_TU_KEY" }
}
}
}Legacy (MCP_AUTH_TOKEN solo si el servidor lo exige, no es el waro_sk):
Authorization: Bearer $MCP_AUTH_TOKEN — deprecated, usa waro_sk.
Default WARO_API_URL is https://api.warolabs.com — override via WARO_API_URL env or profile api_url in ~/.waro/config.toml. Supports WARO_PROFILE (same as waro-cli/src/config.rs:28).
Tools (26)
waro_ping, waro_schema, sales_list|metrics|detail, customers_list|detail|orders|metrics, menu_products|recipes|modifiers, analytics_menu|food_cost|alerts|data_quality|cohort|waros|rfm|churn_risk, financial_products, waros_estimate|balances|customer, queries_schema|run
All tools return waro.agent.v1 envelope; errors set isError:true.
Publish
npm publish --access publicRoadmap
Batch 1: scaffold + stdio
Batch 2: tools/list contracts
Batch 3: tools/call + auth + agent-json (this)
Available Tools
26 toolsanalytics_alertsD
Alertas analiticas y recomendaciones.
Inputs: fields.
analytics_churn_riskC
Clientes en riesgo churn por silencio.
Inputs: limit, fields.
analytics_cohortC
Matriz cohortes retencion semanal/mensual.
Inputs: period, date_to, date_from.
analytics_data_qualityD
Alertas calidad de datos en compras e ingredientes.
Inputs: fields.
analytics_food_costD
Food cost y margen por producto.
Inputs: fields, date_to, date_from.
analytics_rfmC
Segmentacion RFM por recencia, frecuencia y valor.
Inputs: fields, date_to, date_from.
analytics_warosC
Analitica WAROS: emitidos, redimidos, tasa.
Inputs: date_to, group_by, date_from.
customers_detailC
Detalle e historial de un cliente.
Inputs: customer_id (required), fields, dry_run.
customers_listC
Lista clientes con frecuencia, valor, ticket y saldo WAROS.
Inputs: all, limit, fields, offset, +3 more.
customers_metricsC
Resumen clientes nuevos vs recurrentes y top customers.
Inputs: fields, date_to, dry_run, date_from.
customers_ordersC
Ordenes de un cliente por periodo.
Inputs: customer_id (required), limit, fields, offset, +3 more.
financial_productsC
Analisis financiero productos: margen, costo, ganancia.
Inputs: fields, date_to, date_from.
queries_runC
Ejecuta QuerySpec seguro y devuelve filas analiticas.
Inputs: spec (required), fields.
queries_schemaC
Lista datasets, dimensiones, medidas y filtros QuerySpec.
Inputs: fields.
sales_detailC
Detalle de una orden por UUID.
Inputs: order_id (required), fields, dry_run.
sales_listC
Lista ordenes con estado, fecha, pago, cliente, items y total.
Inputs: all, limit, fields, offset, +8 more.
sales_metricsC
Metricas agregadas de ventas por periodo y agrupaciones.
Inputs: limit, fields, ranges, date_to, +6 more.
waro_pingA
Health check — returns ok.
Inputs: no named parameters.
waros_balancesC
Saldo WAROS para lista de perfiles.
Inputs: profile_ids (required), fields.
waro_schemaA
Introspect Waro API contracts — list all tools/contracts or detail one.
Inputs: command.
waros_customerC
Resumen WAROS de un cliente.
Inputs: profile_id (required), fields.
waros_estimateC
Estimacion WAROS por compra.
Inputs: total (required), customer_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 26 tools
Several tools have overlapping analytics purposes (analytics_waros, analytics_rfm, analytics_churn_risk, analytics_food_cost, analytics_alerts, analytics_data_quality, analytics_cohort, analytics_menu) but each targets distinct metrics. Some confusion possible between waros_estimate and waros_balances/customer, and between sales_list/metrics/detail and customers_orders, but descriptions are specific enough. However, sales_list vs sales_detail are clear, and customers_orders vs customers_list/detail are distinct. The overlap in analytics tools is moderate, but not severe.
The naming follows a general pattern of domain_subject, e.g., 'analytics_*', 'waros_*', 'queries_*', 'sales_*', 'customers_*', 'menu_*'. This is fairly consistent, but there are some deviations: 'waro_schema' and 'waro_ping' use a different prefix than the 'waros_*' group, and mixed order in 'financial_products'. The pattern is mostly predictable but has minor irregularities.
26 tools is slightly heavy but within the range for a comprehensive business analytics server covering multiple domains (analytics, sales, customers, menu, WAROS, queries). The count is high but each tool appears purpose-specific and covers a broad domain, so it's acceptable. Not excessive like 50+.
The tool surface covers a wide range of business analytics: sales, customers, menu, WAROS, financial metrics, queries. It includes list/detail/metrics and analytics for major areas. However, there are some gaps: no tool for updating/creating data (though analytics servers are often read-only), no explicit tool for user management or settings, but for the intended purpose of analytics and reporting, it seems fairly complete. There is also a queries_run and queries_schema for custom queries, which adds flexibility.
Maintenance
Related MCP Connectors
Access Pollinations models and API capabilities through agent tools.
Connect ChatGPT or Claude to your CRM, store or shipping API. Keys stay out of the chat.
Verified, pay-per-use API tools for AI agents through one authenticated connection.
Pay-per-use agent tools: schedule HTTP calls, extract pages, PDFs, OG images, QR codes, short links.
Related MCP Servers
- FlicenseDqualityDmaintenanceEnables interaction with a restaurant FastAPI backend for menu management, order processing, customer management, and analytics through natural language.241-
- FlicenseAqualityDmaintenanceEnables LLMs to interact with WhatsApp via the official WhatsApp Cloud API, providing tools for sending messages, templates, media, and managing conversations.13-
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents to interact with Odoo 17 ERP via external API, providing tools for inventory management, sales order processing, and customer management through natural language.-
- AlicenseAqualityDmaintenanceExposes the Loyverse API as MCP tools to manage stores, products, inventory, customers, receipts, and more from AI assistants.54MIT