Claude and ChatGPT integration
Your Denser chatbot already answers customers from your website and documents. Connect it to Claude, ChatGPT or Cursor, and your team gets the same cited answers, conversations and analytics in the assistant they work in all day.
On every plan, including Free. Sign in with Denser, no API key.
What your team can ask
Draft a reply, check a policy, or find out what customers asked this week, without opening another tab.
“What does our help center say about refunds for annual plans?”
Searches the chatbot's knowledge base and answers with links to the pages it used, or returns the chatbot's own answer exactly as a customer would see it.
“Which answers did visitors rate badly this week, and why?”
Reads recent conversations with their ratings and sources, so you can see where the chatbot fell short and which page to fix.
“Which chatbot handled the most conversations this month?”
Messages, conversations, ratings and leads over any period, plus how many chat queries your plan has left.
“Did last night's website re-crawl finish? Who left their email today?”
Each knowledge source's indexing status, and the leads your chatbots captured, when you allow it.
One knowledge base
Claude and ChatGPT search the same knowledge base that answers customers on your website. Re-crawl a page or upload a new PDF in Denser, and every connected assistant answers from it as soon as it is indexed. No copies of your docs in a Custom GPT or a Claude Project to keep in sync.
How retrieval and MCP fit together: RAG vs MCP.
Set it up
Paste https://mcp.denser.ai/mcp as a connector in Claude or a custom MCP server in ChatGPT. There is no API key to copy.
Sign in with your Denser account, pick the workspace, and keep or change what the assistant may read.
The assistant finds the right chatbot and tool by itself. Claude and ChatGPT ask you before running a tool you haven't allowed yet.
Exact steps for each assistant, with screenshots, are in the MCP setup guide.
Access and control
Questions
Claude (on the web and the desktop app), ChatGPT, Cursor, Claude Code, and any other assistant that supports remote MCP servers with OAuth sign-in. They all use the same address: https://mcp.denser.ai/mcp.
No. The MCP server is included on every Denser plan, including Free. Asking a chatbot for an answer uses one of your plan's chat queries, as a visitor's question would. Searching the knowledge base, reading conversations, analytics and leads are free.
On Claude, the free plan allows one custom connector, so Denser works there. On ChatGPT, custom MCP servers are available on paid plans. In Claude Team and Enterprise, and in ChatGPT Business and Enterprise, an owner or admin adds or allows Denser first.
No. Every tool reads, except asking a chatbot a question, which records that conversation in the chatbot's chat logs. The assistant can't edit sources, instructions or settings.
Each person signs in with their own Denser account, so the assistant sees what that person can see in the workspace. Reading leads also needs the chatbot's admin role.
A Custom GPT or Project keeps its own copy of files you upload, and you update it by hand. With Denser, the assistant searches the same knowledge base your website chatbot uses, so a re-crawled page or a new PDF shows up in every assistant once it is indexed.
The Model Context Protocol is an open standard that lets AI assistants like Claude and ChatGPT connect to outside tools and data. Denser runs an MCP server, so any assistant that speaks the protocol can use your chatbots without a custom integration.
See how the chatbot itself works on the knowledge base chatbot page.
Point Denser at your website, docs, and PDFs. It answers in minutes, every reply cited to its exact source.
No code. Free to start. Cancel anytime.
