Built-in AI Assistant vs. MCP: Which Should You Use?
There are two ways to build and run your Daber AI call center by chatting instead of clicking:
- The built-in assistant: a panel inside the Daber AI dashboard. Open it with AI Assistant at the top right, or ⌘J / Ctrl+J.
- MCP: connect the AI assistant you already use (Claude, ChatGPT, Claude Code or Cursor) to your workspace with one link,
https://api.phone.daber.ai/v1/mcp. The MCP setup guide walks through it.
Both can do the same things, because the built-in assistant uses the same tools our MCP server offers. Anything we add to one appears in the other. The difference is where you work and what else is in the conversation.
Side by side
| Built-in assistant | Your own assistant over MCP | |
|---|---|---|
| Setup | None. It's already in the dashboard. | Paste one link, sign in, approve once. |
| Where you work | Next to the page you're changing. You see the result right away. | In Claude, ChatGPT, your code editor or terminal. |
| Knows your current page | Yes: "this agent" means the one on screen. | No, you name what you mean. |
| Other material in the conversation | Only Daber AI. | Your files, email, docs and other connected tools, if your assistant has them. |
| What it can change | Agents, flows, knowledge, tools, tests, campaigns, conversations. | The same. |
| Approval before money / people / deletes | Approve or Cancel card in the panel. | Your assistant's own tool-approval prompts. |
| Who can use it | Workspace admins. | Workspace owners and admins who connect it. |
| Undo | Version history for agents and flows; every change also logged in Audit under your name. | Version history for agents and flows. |
| Cost | Included. | Included on our side; your assistant's own plan applies. |
Choose the built-in assistant if…
- You don't already use an AI assistant, or don't want to connect one.
- You want to see each change on the page as it happens.
- You're new to Daber AI and want to ask "where is…?" and "why did…?" questions while you look at the dashboard.
- Several admins on your team should all have the same tool without setting anything up.
Choose MCP if…
- Your material lives elsewhere: a script in Google Docs, a price list in a spreadsheet, a CRM. Your own assistant can read it and build from it in the same conversation.
- You work in a code editor or terminal and want to set up Daber AI from there with Claude Code or Cursor.
- You manage the setup as part of a bigger project, like building a campaign from a list your assistant just pulled together.
You can use both
They work on the same workspace. A common pattern: build the first version from Claude, where your documents are, then use the built-in assistant for day-to-day changes while you're in the dashboard, such as "make the greeting shorter" or "why was this call transferred?"
Same rules either way
- Actions that spend money, reach a person or delete something wait for your explicit approval.
- Knowledge answers are added as drafts and only reach calls once approved.
- Agent and flow changes are versioned and can be rolled back.
- Paying for a plan and getting a phone number stay as buttons in the dashboard.
New to Daber AI? Create your workspace. Building and testing are free. Then follow From zero to AI call center by chatting.