Marlo answers questions about the fleet — the ops side: which mixers are up, who's using PEP, what's failing, what people wish it could do. It's read-only: Marlo reports, it never changes a mixer. (For changing a mix, that's PEP — see what you can ask PEP.)
Use it at console.marlo.run, or wire the same data into your own Claude — see Connect to the fleet MCP. Plain language; name a church and a time window for sharper answers.
"Which churches are down right now?"
"How many mixers are online?" · "What's offline?"
"Is Coastline online?"
"List all the churches." · "How many are configured?"
"What Slack channels and box does Awaken Church use?"
"What are Coastline's channel names?"
"How much is the fleet being used this month?"
"Which churches are most active? Which haven't touched it?"
"When did Grace Fellowship last use PEP?"
"Usage over the last 7 days."
"What's been failing this week?"
"Any errors at Awaken Church in the last 30 days?"
"What are people asking PEP to do that it couldn't?"
"Show unfulfilled requests at Coastline."
Surfaces requests where PEP had no tool to fulfill them (e.g. EQ/tone asks). A fleet-wide signal for what to build next.
"Show me Coastline's recent activity."
"What's happened at The River Church in the last week?"
A full interaction timeline for one church — the place to start when investigating a specific report.
Read-only. Marlo never changes a mixer — no faders, no mutes, nothing live. It only reports.
No restart / deploy / "push latest." Not built — those would need new tools.
It sees fleet status, channel names, and the interaction log. Anything outside that, it can't answer.