You can connect NoCrash to Claude in about a minute, then ask it about your stuff in plain words — “what broke overnight?”, “is everything green before my call?” — and get a real answer back. There’s no key to create or paste. Claude signs you in with a short code we email you, and that’s the whole setup.
This is the easiest way to connect if you use Claude on the web (claude.ai) or the Claude desktop app. If you use Cursor or Claude Code instead, those connect with a key — see the tool reference for that.
Connect in six steps
-
Open Claude — either claude.ai in your browser, or the Claude desktop app.
-
Go to Settings, then Connectors.
-
Click Add custom connector.
-
In the form that opens, name it NoCrash, then paste this address into the URL field and click Connect:
https://mcp.nocrash.io/mcp -
Claude emails you a short login code. Enter it.
-
A screen asks if you want to connect NoCrash. Click Allow. Done — NoCrash is now connected.
That’s it. From now on you can ask Claude about anything NoCrash watches for you.
One thing to know first
Use the same email you signed up to NoCrash with. The login code is how we match Claude to your account. If the email doesn’t match a NoCrash account, the connection won’t find your stuff — sign in at nocrash.io with that email first, then connect.
Try it
Once connected, just talk to Claude in plain words. A few to start with:
Read me NoCrash's latest brief — what broke overnight?
Before my 2pm call: is everything green in NoCrash? List anything that isn't.
Search NoCrash for any errors mentioning "timeout" this week and summarize them.
Claude picks the right tool for what you asked and hands you the answer. You never have to know which tool — that’s the point.
What you can ask for
NoCrash gives Claude nine things it can do for you. Most just look something up; a few make a change (send a heartbeat, record a problem, run a fresh check). Here’s each one in plain words.
Things that just look something up
- See everything you watch — the full list of what you’ve connected, each one’s color (green = working, yellow = needs a look, red = needs help), and a one-line summary of how things are overall.
- Overall health — a single plain-language read on everything at once: how many are fine, how many need a look, how many need help.
- Look at one thing in detail — everything about a single watched item: when it last ran, when it’s expected to run next, and its recent activity.
- Recent activity — the history of what’s happened across everything you watch, in plain language. You can narrow it to one item or one kind of event.
- Your latest daily brief — the plain-language summary of what happened overnight: what ran fine, what needs a look, what needs help. (Available on paid plans.)
- Find errors by keyword — search across everything you watch for a word like “timeout” or “payment” and get back the matches with plain-language context.
Things that make a change
- Send a heartbeat — tell NoCrash a watched item is alive right now (handy right after you ship something). It turns green and the clock resets.
- Report a problem — record that something went wrong, with the details, so it shows up next to everything else and lands in your next brief.
- Run a fresh check now — don’t wait for the next scheduled check; ask NoCrash to look right now. There’s a gentle limit (a short wait between checks, and ten per hour for each item) so nothing gets hammered.
Connecting a different tool?
- Cursor, Claude Code, or the Claude desktop config file connect with a key instead of this connector. The one-line setup is at the top of the tool reference.
- Want example prompts for every situation? The cookbook has the ones people reach for most.