The Aimdoc MCP server connects your visitor and customer data to the AI assistants you already use. Ask a question in plain language and get full visibility into who's on your site, who's warming up, and who needs your team — no dashboards required.
Works with Claude, ChatGPT, Cursor, and any MCP client.
Aimdoc watches your full visitor journey — every account, session, and conversation across your website and product. The MCP server makes all of it queryable from inside Claude or ChatGPT, so you can ask questions the way you'd ask a teammate.
Keep working in the AI assistant you already use. Aimdoc shows up as a data source your assistant can reach.
Anonymous visitor to activated customer — website and in-app. One question spans the whole journey, not a single dashboard.
Plain-language questions instead of filters and exports. The assistant does the digging and hands you the answer.
Real questions your team is already asking — now answered in seconds.
Ask for a live read on visitors across your website and product in real time — identities, accounts, and what they're doing this minute.
Surface the accounts on your website that are most active and showing buying intent, ranked by engagement — so sales chases the right ones first.
Pull the users hitting friction inside your product — rage clicks, dead ends, repeated errors — before that frustration turns into churn.
Find customers with an open support ticket or an unanswered question, so nothing slips through the cracks between teams.
Identify the new users who stalled mid-onboarding and never reached activation — then reach out while it still matters.
Ask for conversion, qualification, and activation trends across the full journey — from anonymous visitor to activated customer.
Three accounts are heating up. Northwind visited pricing 4× and started a trial, Acme has two new users in-app today, and Lumen booked a demo.
One flag: a new user at Acme stalled during onboarding two days ago and hasn't returned — worth a check-in. Want me to draft the outreach?
Illustrative example. Aimdoc answers from your own live account data.
Add the server once. Then just ask.
Add Aimdoc's MCP endpoint to Claude, ChatGPT, or any MCP-compatible client with your API key. Setup takes a minute.
Type a question like “which accounts are warming up today?” — no dashboards, no query language, no exports.
The MCP server pulls real-time visitor profiles, journeys, conversations, and contacts straight from your Aimdoc account.
Draft the follow-up, build the list, or brief the team — right there in the same chat, with the data already in context.
The MCP server authenticates with your Aimdoc API key and only ever returns data from your own account. Revoke access at any time. Read about Aimdoc security.
Common questions about connecting Aimdoc to your AI assistant.
It's a Model Context Protocol (MCP) server that exposes your Aimdoc data — visitor profiles, journeys, conversations, and contacts — to AI assistants like Claude and ChatGPT. Instead of opening a dashboard, you just ask the assistant questions about your visitors and customers.
Any MCP-compatible client. That includes Claude (desktop and web), ChatGPT, Cursor, and a growing list of tools that speak the Model Context Protocol. If your assistant supports MCP, it can connect to Aimdoc.
Anything about your visitor and customer activity: who's on your site and in your app right now, which accounts are warming up, who's frustrated, who has an open support ticket, who stalled in onboarding, and how your funnel is trending. You can also ask follow-ups and have the assistant draft outreach.
Yes. The MCP server authenticates with your Aimdoc API key and only ever returns data from your own account. You control access, and you can revoke the key at any time.
No. Connecting the server is a one-time, copy-paste setup. After that, anyone on your team can ask questions in plain language — no SQL, no dashboards, no analyst required.
Connect the Aimdoc MCP server to Claude or ChatGPT and get full-journey visibility into who's on your site, who's warming up, and who needs follow-up — just by asking.
Prefer the technical walkthrough? Read the MCP server setup docs.