Start here
NoCrash keeps an eye on the things you ship and tells you, in plain language, when one of them stops working. These docs are the technical half of that story: how to connect your tools, how to talk to NoCrash from your own AI agent, and how to let us reach apps you keep behind a lock.
If you only read one page, read the cookbook. It shows the exact sentences you can say to your agent and what you get back.
Three ways to connect
You can mix and match these — most people use more than one.
- n8n — give NoCrash a read-only API key and we pull your run history. Add the community node and we also see every individual run. See Connect n8n.
- A web address — point NoCrash at any public URL and we check it for you. Good for a vibe-coded app or a public site.
- A snippet — drop a small script tag into your app and it tells NoCrash when something crashes in the browser.
Talk to it from your agent
NoCrash speaks MCP — the protocol Claude Code, Claude Desktop, and Cursor use to call outside tools. Once you connect it, you can ask your agent things like “what broke overnight?” and it pulls the answer straight from NoCrash. There are nine tools; the cookbook walks through the ones you’ll reach for most, and the tool reference lists every one.
What you’ll need
- A NoCrash account (the free plan works for trying all of this).
- An API key, which you create under Settings → API keys. It’s shown once, so copy it somewhere safe.
That’s it. Pick a page from the sidebar and go.