MCP server
Ask an AI assistant about your SDR operation. Dialbrew's MCP server gives Claude, ChatGPT and other MCP clients read-only access via your API key.
Last week you booked 29 meetings across three clients:
What's in it
Standard MCP
Works with any Model Context Protocol client — Claude, ChatGPT, Cursor and custom agents.
API-key authentication
Connect with a tenant API key created by an admin; revoke it at any time.
Tenant-scoped
An assistant only ever sees the account the key belongs to.
Operation data as tools
Leads, bookings and outcomes, client projects, SDR performance and billing status.
Read-first
Built for questions and summaries, so an assistant cannot change the record behind your invoices.
Questions that shouldn’t need a report
“Which clients are behind on held meetings this month?” “What did we book for Northgate last week, and how many were no-shows?” Today each is a filter, an export or a report someone builds. With an AI assistant connected to the operation, it is a sentence.
Connect an AI assistant to Dialbrew
The Model Context Protocol (MCP) is the open standard AI assistants use to connect to tools and data. Dialbrew exposes your operation as an MCP server.
- 1
Create an API key
An admin creates a tenant API key in Dialbrew.
- 2
Add it to your assistant
Claude, ChatGPT, Cursor or any MCP client.
- 3
Ask in plain language
Leads, bookings and outcomes, client projects, SDR performance, billing status.
- 4
Revoke any time
Revoking the key cuts the assistant off immediately.
Read-only access, scoped to your account
The server is built for questions and summaries — a client review, a Monday pipeline check, a quick look before a call. It reads the same records as the client portal and reports, scoped to your account, so the answers match what your team and clients already see.
Related: client portal, HubSpot sync and integrations.