Connect Hermes Agent to ChurnWin churn feedback
Hermes Agent can run long-lived SaaS growth loops. Add ChurnWin as a native MCP server and Hermes can read churn metrics, cancellation feedback, at-risk customers, and action plans before creating GitHub issues or recommending the next retention experiment.
Schedule a Hermes cron job to inspect ChurnWin feedback every morning and stay silent unless new work appears.
Create or update GitHub issues from repeated churn themes, with PII-redacted evidence and acceptance criteria.
Feed your agent the customer context it needs before it chooses the next retention or product task.
1. Add ChurnWin to Hermes
Hermes Agent reads MCP servers from ~/.hermes/config.yaml. Add this block, then restart Hermes so it discovers the ChurnWin tools.
mcp_servers:
churnwin:
url: "https://api.churnwin.com/mcp/"
headers:
Authorization: "Bearer cwk_live_YOUR_KEY_HERE"
timeout: 180
connect_timeout: 60After restart, Hermes exposes tools with names like mcp_churnwin_get_metrics,mcp_churnwin_get_churn_reasons, andmcp_churnwin_get_action_plan.
2. Ask Hermes to build the feedback loop
Use the ChurnWin MCP tools to inspect 90-day churn reasons and cancellation feedback. Aggregate by theme and MRR impact. If a theme is repeated or high impact, create a GitHub issue with redacted evidence, acceptance criteria, and metrics to watch. Do not print customer emails, Stripe IDs, or raw comments.
3. Make it daily
For an autonomous SaaS worker, schedule the same task with Hermes cron. ChurnWin becomes the feedback signal; GitHub issues become the visible work queue.
hermes cron create "0 8 * * *"
# Prompt idea:
# Read ChurnWin via MCP. Create at most 3 deduped, PII-redacted GitHub issues
# for repeated or high-MRR churn themes. Stay silent when nothing is actionable.Use an Agent Access key
Create a ChurnWin Agent Access key in Settings, keep it in Hermes config or a secure env file, and treat it as production data access. It can expose customer-level churn context to your agent.