WoW Raid Analyzer: Ask AI Why You Wiped (Raid Tools for Raid Leaders)

Every WoW raid leader knows the 90 seconds between pulls. Twenty people waiting, one wipe to explain, and a call to make. Logs tell you what happened. The research (why it happened, what the kill did differently, what one player should change) has always meant digging through a raid log analyzer by hand. The WowCoach MCP turns your AI assistant into a WoW raid analyzer you can simply ask.

A WoW raid analyzer you can talk to

MCP (Model Context Protocol) is how AI apps plug into other services. The WowCoach MCP plugs your assistant (Claude, ChatGPT, Codex, Cursor, or any app that supports MCP) into your WowCoach logs. Once it's connected, the assistant has more than 50 research tools for any pull you can open on wowcoach.gg.

Wipe tools return what ended the pull, the chain of deaths, the point of no return, and the fix. Death tools give death order, killing blow, whether it was avoidable, who died first most, and a player-by-pull death grid. Mechanics tools show who got hit by an ability, how often, how many stacks, who held a debuff and who soaked what. Position tools show where everyone stood when they died, who was stacked and who moved how far; they need advanced combat logging (or the desktop app's live pulls).

Comparisons put two pulls side by side, a kill against a wipe, or a player against top players of their spec. Interrupt tools list every interruptible enemy cast and what stopped it, with a reference to drill into any single cast. Prep tools check raid buffs and consumables and pull boss guide advice by role, phase or mechanic. Player tools cover cooldown use, rotation reviews, resource waste and benchmarks. There are also filtered raw event pages, plus AskLogs for any plain question about the log.

You don't call the tools yourself. You ask the way you'd ask an officer, and the assistant chains them together: find the pull, pull the deaths, check positions, read the guide, compare against the kill. One question can use several tools in a row. It's built for raid leaders who need the one call for next pull, and for any player who wants to know exactly what to fix.

Raid analysis examples from Mythic Venomous Abyss

Below are raid-leader questions and what the WowCoach tools returned, on real Mythic Venomous Abyss progression logs from two raid teams that use WowCoach. Player names are changed. Numbers are the tools' own, rounded. You can ask the same questions about your raid tonight.

1. "We wiped at 8.5% on The Lost Explorers. What ended it, and what did the kill do differently?"

The Lost Explorers on Mythic is a council fight. Mor'zahi's Final Ascension wipes the raid unless someone feeds a Disgusting Fish to one of the explorers to stop it.

On the 8.5% wipe, Mor'zahi gained Final Ascension at 5:11. Three players had died before it. Nineteen died after it, all within 18 seconds.

Then the follow-up. Compared side by side, the two pulls differ in the fish events.

Group DPS was identical on both pulls. The damage was there; the raid had to live through that cast. The kill shows how unforgiving it is: the one late fish (Nama, 4.3 s into the cast) let a Final Ascension through, and the raid had to survive it.

The call for next pull: "Fish carrier: every fish goes in the moment Final Ascension starts casting. The third one goes to Gebbo."

2. "Everyone keeps dying to Tempest on Sszorak. Is it just people not dodging?"

Sszorak, Mythic. The raid wiped at 74.6%, with six Tempest deaths in the first 71 seconds. The boss guide says Tempest sends poison vortices spiralling around the room, and every touch adds a stack that ticks hard.

Hit by hit, the first death was a hunter renamed Arrowmir. At 0:19.10 a Tempest hit landed for 359,699 damage, 1 stack. At 0:19.19, just 0.09 seconds later, a second hit did 359,699 more, 2 stacks. At 0:20.12 the poison tick killed Arrowmir, with 119,705 overkill.

Position data shows Arrowmir moved 0 yards in the 8 seconds before dying. A healer, Tidesong, died next to Tempest after moving 78.3 yards in the 8 seconds before, taking two hits 0.15 seconds apart; the second was fatal. Two opposite habits: one player stood still, the other most likely ran through a vortex while repositioning.

The part a raid leader cares about is what it cost the raid:

• 0:45 Tidesong (Restoration) dies to Tempest.
• 1:02 Brookwell (Restoration) dies to Tempest, and gets a battle rez.
• 1:08 Sszorak's fourth Mutilate lands on a soak group of 10. Its poison, Mutilated Gash, ticks about 10% of max health per second for 22 seconds, and the guide says the soakers have to be healed through all of it.
• 1:10 Brookwell dies again, to Ula'tek's Presence.
• 1:11 Halowyn (Discipline), a soaker who had taken five Tempest hits by then, dies to the poison.
• One healer is left: Mistpaw, in the other soak group.
• By 1:24, 7 of the 10 soakers have died to the poison.

So "dodge Tempest" undersells it. Tempest took one healer out for good and forced a battle rez on another, and within three seconds of the soak landing the raid was down to one healer for a poison that ticks 10% a second.

The calls for next pull:

1. Healers get Tempest priority: pick a lane early, take small steps, never run along or through a vortex.
2. Nobody stands still once a vortex is close, and nobody sprints across the room either. Step out of its path.
3. Keep healers who've taken Tempest hits out of the next soak, and plan the battle rez around the soak.

3. "Who keeps dying first?"

Across 13 Mythic attempts on The Lost Explorers there were 253 deaths. "Who died first, every pull?" turns that into a list you can act on. Relic Rupture killed people 41 times across those attempts, more than anything else; Final Ascension was next with 31. One healer died first on 3 of the 12 wipes. The wipes averaged 21 deaths each. The kill had 3.

You also get the full grid: every player, every pull, the time of each death, the first death marked. From there you can ask what killed that healer first on those pulls and whether a defensive was up. That's a conversation for whispers, and now you have the facts for it.

4. "Is everyone flasked and buffed?"

Ask between pulls, or after a wipe that felt soft. On the 8.5% wipe, one DPS had no flask and one tank had no weapon buff. Everyone was fed. Fortitude, Mark of the Wild, Arcane Intellect, Battle Shout and Skyfury were all up. Blessing of the Bronze wasn't, and the tools say why: nobody in this raid can cast it, because there's no Evoker. Not a mistake to chase.

5. "Which casts got through, and why?"

The tools list every interruptible enemy cast on a pull, each with a reference you can drill into, and what happened to it: kicked, stopped with crowd control, stopped by a knockback or grip, or completed.

On Mchimba the Embalmer in a Season 2 Kings' Rest key, the Half-Finished Mummies started Wretched Discharge 10 times. Nine were stopped: five kicked, three stopped with crowd control, and one cancelled by a Death Grip that pulled the mummy mid-cast. The one that went off hit 4 players for 2.31 million damage (374k of it absorbed). Nobody had a kick ready when it started, and a stun landed 0.3 seconds after it had already gone off.

Ask about that single cast and you get its damage, who could have stopped it, and every stop attempt on the caster.

6. "I'm an Arcane mage. What should I change?"

It isn't only for raid leaders. Here's what the tools return for an Arcane mage, renamed Frostlin, on the Lost Explorers kill.

On cooldowns, Frostlin used Arcane Surge 5 of 5 possible times and Touch of the Magi 9 of 10, never sitting on Surge for more than 11.5 seconds. Against top Arcane mages (the top 10% of Arcane parses across all Mythic bosses, not just this one):

The same number of casts a minute, but a very different mix: far more Arcane Blast, fewer Missiles and Barrages. That's the question to research next: on which parts of the fight, and why.

Context matters too. Frostlin carried all three fish on the kill (0:57, 3:05 and 5:08) and did 182k DPS. On the 8.5% wipe, when someone else carried the fish, Frostlin did 235k. Carrying cost about 53k DPS, and it's also why the raid lived. A meter can't tell you that. The tools can.

Where everyone stood

Ask where people were and your AI can draw it. ChatGPT plotted this Heroic Entombed Sentinels pull from WowCoach's position data, a second before Miasma erupted: the marked player had three raiders within 3.5 yards, one tank was 15.3 yards away and the nearest healer 28.6. The names are fictional; the positions and distances are the recorded ones.

During the pull, too

Everything above is research for between pulls and the morning after. For the pull itself, WowCoach Pro includes live coaching in the desktop app: it reviews every boss pull as it ends and puts up a coaching card with what went wrong and what to fix on the next one. Use both: live coaching for the next pull, your AI for the deep questions.

Set it up in two minutes

1. Be on a WowCoach paid plan (Solo or higher), and upload your raid log, or let the desktop app upload it as you raid.
2. Copy the server URL from wowcoach.gg/connect, add it to your AI app and sign in with Battle.net. App-by-app steps are in Use WowCoach in your AI assistant.
3. Ask: "Use WowCoach to tell me why we wiped on our last pull."

For more ideas, see 15 questions to ask your AI about your logs, what kills raids on every Venomous Abyss boss, and the rest of our Season 2 raid tools.

FAQ

What makes this different from a normal raid log analyzer? You don't read charts and filter tables. You ask a question, and your AI uses WowCoach's raid tools to pull the deaths, hits, positions and timings that answer it, then gives you the call for next pull.

What is an MCP server? A connector that lets an AI app use another service's tools while you chat. The WowCoach MCP gives your assistant tools that read your WoW logs.

Is it free? No. It's included with every paid WowCoach plan, Solo and up. See plans.

Does it use my Coach Clutch credits? Your AI app writes the replies, so normal questions don't. AskLogs uses your existing allowance.

Which AI apps work? Claude (web and desktop, and mobile once added), ChatGPT's desktop app in Work mode, Codex, Cursor, Claude Code, and anything else that supports remote MCP servers.

Does it work for Mythic+? Yes. Keys, trash pulls, kick lists and timers all work the same way.

Do I need advanced combat logging? Only for position questions on uploaded logs. Everything else works from a normal combat log.

Can my raiders use it too? Yes, if they're on Solo or higher. Each raider connects their own account and sees the logs they can open on wowcoach.gg, including logs your guild shares. Free accounts get a note to upgrade.

Can it change anything? It can't change your logs or your account, and it sees only what you can see on wowcoach.gg. A few tools prepare a missing coach card or refresh a character summary. Disconnect any time under Profile → Connected apps.

---

Examples from Mythic Venomous Abyss progression logs of two raid teams and a Season 2 Kings' Rest key, with player names changed. Numbers are as the WowCoach tools returned them, rounded.