MCP Connectors by Databox - Give your AI Analyst context to explain performance and act
by•
Connect your AI Analyst to the tools your business runs on. It pulls context from your CRM or support desk, so every answer reflects what's happening in your business, and it can act on what it finds. Choose from 10+ connectors or add any MCP server.
Replies
Congratulations on the launch!
When the tools point to different reasons (say the CRM notes blame a legal review but a Slack thread blames pricing), does Genie show both explanations and let you judge, or does it pick the most likely one?
@tery_emilson Thanks, Tery! It shows both. When two sources point to different reasons, Genie, our AI Analyst, lays out each explanation next to its source, so you can see where each one came from and decide for yourself. It doesn't quietly pick one and hide the other. A conflict like that is often the most useful part of the answer, because it usually means the team isn't on the same page yet.
Bringing MCP connectors makes the “why behind the numbers” much more useful.
@numerbyte Thanks, Aditya! That's the whole idea. The number tells you what changed, and the context tells you why.
"it can act on what it finds" is the line I'd want to poke at. explaining why a metric moved is read-only and low risk, but acting implies it's writing something back into the CRM or support desk, not just reading from it. what does that write path actually look like in practice, is it drafting a task for a human to approve, or can Genie create/update records in the connected tool directly without a person in the loop first?
@galdayan Fair line to poke at, Gal. It depends on how you set it up, and the choice is yours per tool.
Write tools call the connected tool directly. Genie, our AI Analyst, can create or update a record in your CRM or support desk, not just draft a suggestion. Whether a person has to approve first is up to you. For each tool, you choose whether it can run on its own, needs your approval every time, or is blocked completely. By default, write actions ask for approval first. So out of the box there's a person in the loop, and you remove that step only for the actions you trust it to take alone.
In practice, most teams let it look things up freely, allow a few low-risk actions like creating a follow-up task, and keep approval on anything customer-facing or anything that changes pipeline data.
We spent a good chunk of time on connector management, so seeing people use the permission settings is a nice payoff. My setup for Notion: read tools on Always allow, everything else on Needs approval. Fast for lookups, still asks before changing anything.
The per-tool approval settings are the part I’d want in any setup like this. Pulling context is one thing, but once an analyst can update a CRM or stop a campaign, “needs approval” can’t be an afterthought.
@znu Agreed, Do Hyeon. That's why we built permissions in from day one instead of adding them later. You decide per tool what Genie, our AI Analyst, can do on its own and what needs your approval first. Looking things up can run freely, while updating a deal or pausing a campaign waits for your OK.
The weekly report that used to take half a Thursday now has a roommate doing it. I'm in!