Hey friends, Sarah here đź‘‹
It’s been a busy season at Scout, and I wanted to take a minute to share two of the biggest things we rolled out recently. If you’ve been following along, you know our north star is simple: make it easier for dev teams to understand what’s going on in production without drowning in tabs, tools, and guesswork.
This quarter, we shipped two features that represent a big step in that direction: Error Monitoring and our shiny new MCP Server.
Error Monitoring: Meet the Dream Team
You can now have all of your error reporting, logs, and application monitoring data in one app!
Stop juggling multiple tools and simply let Scout bring your errors and performance data together. Instead of waiting until the damage is visible, Scout automatically tracks failures and alerts you in real time. The goal isn’t just to record what went wrong, but to give you the power to fix issues fast before users bounce.
With Scout Error Monitoring, you can:
- Capture request params and custom context straight from the Scout Agent
- Group errors by location and type so you’re not chasing duplicates
- Get notified where your team already lives (Slack, email, etc.)
- Assign, triage, and prioritize error groups (no more “ who owns this? ” moments)
- Automatically prioritize critical endpoints
- Fix things faster with stack traces + GitHub integration
In other words: fewer fire drills, faster fixes, and way less tool-juggling.
MCP Server: Scout Meets Your AI Assistant
Fall brought another big milestone: **Scout now has an MCP server. **
What does this mean? For anyone using AI coding assistants (Cursor, Windsurf, Claude Code, etc.), your assistant can now see what Scout sees — errors, logs, traces — and answer questions in natural language.
Picture asking or prompting your AI assistant as follows:
- *“Why did error rates spike yesterday?”
- *“Show me the slowest endpoint last week.”
- *“Summarize the logs for this crash.”
No late-night spelunking through dashboards. Just fast, clear answers *right where you work. *It’s AI-native monitoring for AI-native development.
This is just the beginning of a bigger loop we’ve been thinking about for a long time: connecting monitoring data directly to the tools you use to build and ship.
Looking Ahead
These two launches are huge steps toward a Scout that not only monitors your apps but helps you take action: whether fixing errors faster or getting context from your AI assistant without leaving your editor.
We’ve got even more on the horizon, but in the meantime, give Error Monitoring and the MCP server a spin, and let us know what you think.
‍
Until next time, happy shipping! Sarah
Product @Scout Monitoring
‍