Connect your tools to Dazza over MCP

Connections gives Dazza live access to your own systems over the Model Context Protocol (MCP). Dazza can then look up an order or a subscription, or make a change, in the conversation. Find it in the sidebar.

Quick starts

Shopify. Built in, no MCP server needed: order status and tracking, recent orders, stock, and cancelling or redirecting unsent orders. See Connect Shopify.
Your own MCP server. Any server that speaks MCP over HTTP.
Stripe. The address is https://mcp.stripe.com. Authenticate with a Stripe agent API key, created in Developers → API keys. Give it only the permissions Dazza needs, and refunds only if Dazza should refund.
Zapier. Paste the server URL from mcp.zapier.com, which includes its own key. Dazza gets the apps and actions you chose there, such as HubSpot, Google Sheets or Calendly.
n8n or Make. Paste the URL of n8n’s MCP Server Trigger, or Make’s MCP server URL and token.

Add a server

Enter the server’s address and choose how it authenticates: None, Bearer token or a custom Header. Addresses must be public and start with https.

Nothing is saved unless Dazza can connect and list the server’s tools. If the credentials are wrong, you’ll see The server refused the credentials.

You can add up to 20 servers to a workspace.

Switch tools on

Every tool starts Off. Set it to:

Test, so only the Agent preview and Tests use it.
Live, so Dazza uses it with customers.

Each tool shows Looks up or Changes things, taken from the server’s own description. You’ll also see what it asks for, and its runs and failures over the last 30 days.

Checks before a tool runs

Each tool has three checks:

Customer confirms first. Dazza shows what it’s about to do and waits for the customer.
Only for verified customers. See Verify your customers.
Team approves first. The request waits in the inbox for someone to approve.

When you switch a tool on, lookups run straight away. A lookup that looks like it returns someone’s own records, such as an order, a booking or an account, starts as verified customers only, so an order number typed into the chat never shows a stranger’s details. Tools that change things ask the customer to confirm and need a verified customer. Change any of these to suit.

On email and messaging apps there are no buttons, so tools that ask the customer to confirm aren’t used there.

What the customer sees

Lookups happen behind the scenes. The customer sees the answer; your team sees a note in the conversation.

Keep it current

Refresh tools lists the server’s tools again. Changed tools are updated, and tools the server no longer has are switched off.
Remove deletes the server and its tools. Past runs stay in the log.

Tools work with every AI model choice.

MCP or a workflow?

To collect details from the customer first and send them to your system as one request, use a workflow instead. See Call your own system.