Run your marketing by asking for it
Connect Diviner One to Claude or any MCP-compatible assistant and it can read your reviews, work your pipeline, check your rankings, and run your campaigns — in your account, with your own key.
The problem
AI assistants are good at marketing work — until they need your data. Then it's you, copying review text into a chat window, pasting the reply back, and repeating it eleven more times. The assistant never sees your real numbers, so its advice stays generic.
The solution
Connect Diviner One directly. Your assistant reads your actual reviews, contacts, rankings, and campaigns, and can act on them — drafting replies, moving deals, scheduling posts. You describe what you want; it does it in your account.
Connected in about a minute
Open your account settings
Find the Connect to MCP card in Diviner One. It generates an API key scoped to the account you're in.
Copy the setup line
The card gives you a ready-made command for Claude Code and a config snippet for Claude Desktop, with your key already in it. Copy the one you need.
Paste it into your AI client
Run the command or drop the snippet into your config. That's the whole setup — there's nothing to install and no OAuth dance.
Start asking
Your assistant can now read your reviews, contacts, rankings, and campaigns, and take action on them — in plain language.
Your marketing platform, in the conversation
Not a chatbot bolted onto a dashboard — a real connection to your real account.
Ask instead of clicking
"Which reviews haven't I replied to?" "Draft replies to the four-star ones." "Schedule those posts for next week." Your assistant does the work in your account.
Your key, your account
Every request carries your own API key, and the API enforces what it can reach. Nothing is shared between users, and no credentials are stored in the connector.
Agencies switch clients mid-conversation
An agency owner's key reaches every client they manage. Say which client you mean and keep going — no logging out and back in.
Works with any MCP client
Claude Code, Claude Desktop, and anything else that speaks the Model Context Protocol. It's an open standard, not a proprietary plugin.
What your assistant can reach
Most of Diviner One is available through the connection, not just a read-only slice of it.
Email marketing
Manage lists and subscribers, draft campaigns, send tests, and pull analytics.
Learn moreRank & LLM visibility
Check keyword positions, run visibility checks, and read the results.
Learn moreWidgets
List your review widgets and the reviews inside them.
Credits & notifications
Check your balance, read the ledger, and see notifications.
Things people actually ask
"Which Google reviews from the last month haven't I replied to yet?"
"Draft replies to all the five-star ones. Keep them short and don't sound like a robot."
"Which deals in my pipeline have gone quiet for more than two weeks?"
"Where am I ranking for the keywords in my main concept, and has anything dropped?"
"Schedule these four posts across next week, spaced out, mornings only."
Anything that sends, publishes, or spends credits is worth reviewing before you approve it — same as you would with a new team member.
Frequently asked questions
- The Model Context Protocol is an open standard for connecting AI assistants to real tools and data. Instead of copying information into a chat window, your assistant talks directly to Diviner One — reading your actual reviews and rankings, and making real changes in your account.
- Any MCP-compatible client. The setup card gives you a one-line command for Claude Code and a config snippet for Claude Desktop, and the same server URL works anywhere else that supports MCP.
- Your key is scoped to a single account and the API enforces membership and permissions on every request — a key can only reach what you can reach. Keys are stored as a hash, shown once at creation, and you can revoke one at any time from your account settings. Email keys can be limited further to read, write, or send. As with any tool that can act on your behalf, review what your assistant proposes before approving anything that sends or publishes.
- Read and reply to Google reviews, manage prompt pages, search and create contacts, work your CRM deals and contact forms, check rank tracking and LLM visibility, generate web page outlines, manage Work Manager tasks and time, schedule social posts, and run email campaigns — among others.
- The connection itself doesn't. Actions that consume credits in the app — generating a web page outline, running an LLM visibility check — consume them the same way when an assistant does it for you.
- Yes. The same API keys work directly against the Diviner One API if you'd rather write a script than talk to an assistant.
What is MCP?
Which AI assistants can I use?
Is it safe to give an AI access to my account?
What can it actually do?
Does it cost extra?
Can I use it to build my own automations?
Connect Diviner One to your AI assistant
Generate a key in your account settings, paste one line into your client, and start asking.