In short: add one URL and your API key to an MCP-capable AI assistant, and it can look up your leads, search what was said on your calls, and read your campaign results — without you building anything.
What it is
The Model Context Protocol (MCP) is the standard way AI assistants connect to outside services. Voizee ships an MCP endpoint, so an assistant that supports remote MCP connectors — ChatGPT and Claude, as well as developer tools such as Claude Code and Cursor — can read your Voizee data directly when you ask it to.
Where you add a connector differs from tool to tool, and not every plan offers them. Check your assistant’s own documentation for where its connector settings live and whether your plan includes them.
It is read-only. Nothing connected this way can create or change a lead, send an SMS, place a call, or start a campaign.
Why use it
- Ask questions in plain language — “what did the customer on Tuesday say about the refund?” — instead of exporting and filtering data yourself.
- Bring Voizee context into work you are already doing in an AI tool.
- No integration to build or host.
Before you start
- Your plan must include the Public API.
- Your Voizee user needs the same permissions the data requires. Call transcripts and campaign figures follow the same access rules as the web app, so if you cannot see transcripts in Voizee, the assistant will not see them either.
Set it up
There are two ways to connect. Signing in is the normal one; the API key is there for tools that cannot open a browser.
Signing in from your AI tool (recommended)
-
Open your AI tool’s connector or MCP server settings.
-
Add a new remote MCP server with this URL:
https://api.voizee.com/api/mcp -
The tool sends you to Voizee to sign in. You will then see exactly what it is asking to read — leads, call history, transcripts, campaigns, tag names — and nothing is granted until you press Allow access.
-
Ask the assistant to list its available Voizee tools to confirm the connection.
There is no key to create, copy or store. You can approve less than the tool asked for, and the assistant then simply does not see those tools at all.
Access is read-only in every case, and you can withdraw it at any time.
With an API key (for tools that cannot sign in)
-
Create a key in Settings → Integrations, on the API & Webhooks tab.
-
Add the same server URL as above.
-
Add the key as a header — not as part of the URL:
X-API-KEY: your_api_key_here
An API key is the whole account’s key: it carries every permission your user has, with no per-connection choice about what an assistant may read. Prefer signing in where the tool supports it.
Most tools accept a JSON configuration block like this:
{
"mcpServers": {
"voizee": {
"url": "https://api.voizee.com/api/mcp",
"headers": {
"X-API-KEY": "your_api_key_here"
}
}
}
}
Always pass the key in the
X-API-KEYheader. Passing it as a query parameter is not supported here and will run into request limits much sooner.
What your assistant can do
| Ask about | What it reads |
|---|---|
| Contacts | Search leads by name, phone, email, status or date; open one lead in full with its custom fields, tags and notes |
| A customer’s history | Everything that happened with one lead in one list — website visits, callback requests, calls, texts, notes, chat and email |
| Where a lead came from | First and most recent marketing source, medium, campaign, search term and landing page, plus how many times they visited |
| Calls | List calls for a date range whether or not they were transcribed; search transcripts by what was said, optionally narrowed to a tag; open one call with its full transcript; tell which calls your AI Voice Assistant answered and count them |
| Reporting | Call volume and themes over a date range, broken down by day and by communication tag |
| Campaigns | SMS and email campaign lists, and delivery figures for one campaign |
| Your own labels | Your lead statuses, tags, communication tags and contact centres, so the assistant can filter by a name you use rather than an internal number |
What data leaves Voizee
When you ask the assistant something, it fetches only what that question needs. The categories it can read are:
| Category | Includes |
|---|---|
| Lead records | Name, phone number, email address, status, tags, custom field values, notes |
| Lead activity | Website visits, callback requests, calls, text messages, chat, email — as a history |
| Marketing attribution | Traffic source, medium, campaign, search term, click identifier, landing page |
| Call metadata | Direction, duration, the phone numbers on the call, start time, whether the AI Voice Assistant answered |
| Call transcript text | The words spoken on a recorded call |
| Campaign results | Campaign names, statuses, and delivery counts |
| Account labels | Your lead statuses, tags, communication tags and contact centre names |
Two things worth stating plainly:
- Call transcripts are conversation content. If someone asks the assistant to read a call, the text of that conversation is sent to the AI provider running your assistant. Treat this the same way you treat any other export of call content.
- Call recordings are never sent. The assistant can read a transcript where one exists; the audio file itself is never handed to it.
How it works
Your assistant connects to Voizee over an encrypted connection using your API key. Every request is limited to the account that key belongs to, and to what your own Voizee user is allowed to see. Results are capped in size so a single question cannot pull your whole database into the assistant.
Dates and times
All dates the assistant receives are in your own time zone — the one set on your Voizee user profile — exactly as they appear elsewhere in Voizee and in the API. When you ask for “calls on 15 March”, that means your 15 March, from midnight to midnight in your zone.
If your profile has no time zone set, dates come back in UTC.
Tips & best practices
- Ask “what happened with this customer?” rather than asking for calls, then texts, then emails separately. The assistant can pull the whole history in one step, and it will tell you how much exists in each channel.
- Call transcript search only covers transcribed calls. If a call was never transcribed it will not appear in search results — an empty answer does not mean the call did not happen. Ask for a list of calls instead, which includes every call and marks which ones have a transcript.
- Attribution comes from website visits. A lead who called you without ever visiting the site has no marketing source to report, which the assistant will say plainly rather than guessing.
- Ask for a date range when you want reporting. It is much faster than asking the assistant to read transcripts one at a time.
- Treat an API key like a password. Revoke it on the API & Webhooks tab of Settings → Integrations if a device is lost, and use a separate key per tool so you can revoke one alone.
FAQ
Can the assistant change or delete my data? No. Every available tool is read-only.
Do my teammates see my API key? No. The key you add to your own AI tool stays in that tool.
Why does my assistant see fewer tools than a colleague’s? Tools follow your Voizee permissions. A user without access to call intelligence is not offered the call or transcript tools at all, and the campaign tools need the same permissions the campaign pages do. The lead tools are not restricted by role: anyone who can connect to the account can search leads and read a lead’s history and marketing source.
Can the assistant listen to a call recording? No. It can read a transcript where one exists, but recordings themselves are never handed to it.
Nothing appears after I connect. Check that your plan includes the Public API. If you connected with an API key, check that it is sent as the X-API-KEY header and has not been deleted. If you signed in, check that you pressed Allow access — cancelling returns you to the tool with nothing granted.
The assistant says a call has no transcript, but I can see one in Voizee. It should not say that. If you signed in and did not approve transcripts, the assistant is told the transcript exists but is not available to it — not that the call was never transcribed. Reconnect and approve transcript access if you want it to read what was said.
I only see some of the tools. You see the tools your approval covers, intersected with what your Voizee user is allowed to see. Approving fewer categories is a supported choice, not a fault.