I thought my dashboard was the product. I was wrong.
I added an MCP server to my SaaS this week, expecting it to be another integration.
Instead, it changed how I think about the product.
I built Sentinel as a website monitoring platform. Like most SaaS products, everything revolved around the dashboard. You log in, create monitors, investigate incidents, check SSL certificates, review response times, and manage status pages.
Once I started using MCP, I realized I wasn’t opening the dashboard nearly as much.
Instead, I was asking an AI assistant things like:
- Create a monitor for this new production site.
- Show me everything that’s down.
- Which SSL certificates expire this month?
- Check the health of this API.
- Summarize incidents from the last 24 hours.
The interesting part isn’t that AI can answer those questions. It’s that I stopped thinking of the dashboard as the only interface to the product.
That got me wondering if we’re heading toward a world where every SaaS has two interfaces:
One for humans.
One for software.
I don’t think dashboards are going away. They’re still the best place to visualize data and investigate problems. But for routine tasks, an AI agent can often skip the UI entirely and interact directly with the application’s capabilities.
Has anyone else added MCP to their product? Did it change how you think about your UX, or did it just feel like another API wrapper?
The shift that caught my attention isn't MCP itself—it's that you're separating capability from interface.
Once that happens, the product is no longer "the dashboard." The dashboard becomes just one client of the underlying system, alongside AI agents. That changes how you think about product design far more than adding another integration.