Docs
Connect AgentPage to ChatGPT or Claude, ask for a lead-catching chat for your website, and read your leads. Everything is done from your assistant.
Before you start
You need:
- A website you control, where you can add a snippet of code, or where your assistant can edit the code for you.
- An email address for sign-in and for your lead emails.
- ChatGPT or Claude, on a plan or workspace that lets you add a custom connector. If you do not see the option, your plan or your workspace administrator may not allow it.
Keep secrets out of the chat. AgentPage never asks for passwords, API keys, payment card numbers or other credentials, and you should not paste any into your assistant for this. To install the chat you only paste a snippet into your site.
Connect AgentPage
AgentPage connects through an MCP server. The address is the same in all three assistants:
https://mcp.getagent.page/mcp
Menu names change between plans and over time. If a label below does not match your screen, look for the option to add a custom connector or custom MCP server.
In ChatGPT
- Open ChatGPT and go to Plugins in the sidebar.
- Choose Add, then Add custom MCP server.
- Name it AgentPage, paste the address above, and leave authentication on OAuth.
- Read the notice about connecting to a server you add yourself, tick the box if you agree, and create it.
- A sign-in page opens. Sign in with your email address and choose Allow.
- Start a new chat, switch AgentPage on from the plugin menu, and try one of the example prompts.
In Claude Code (desktop app)
You do not need a terminal. Use the Claude desktop app.
- Open the Claude desktop app and sign in.
- Open Settings, then Connectors, and choose Add custom connector. Name it AgentPage, paste the address above and add it.
- Choose Connect. A sign-in page opens in your browser. Sign in with your email address and choose Allow.
- Open Claude Code and start a session. In the connectors menu next to the prompt box, switch AgentPage on for the session.
- If your website’s code is in the project folder you opened, Claude Code can add the chat snippet to the right file. It asks before changing anything, and you can review the change first.
In claude.ai
- Go to claude.ai and open Settings, then Connectors.
- Choose Add custom connector, name it AgentPage, paste the address above and add it.
- Choose Connect, sign in with your email address and choose Allow.
- In a conversation, open the tools menu and switch AgentPage on. Then ask for what you need.
On a Team or Enterprise plan, an administrator may need to enable custom connectors first.
Signing in and permissions
- Enter your email address on the AgentPage sign-in page. We email you a sign-in link and a 6-digit code. Either works once, for 15 minutes. If you are new, this step also creates your account.
- A permission screen then names the app that is asking and what it may do: see your chats, leads and reports; create, change and delete your chats; and stay connected until you disconnect it.
- If you allow only reading, the assistant can look at leads but cannot create or change a chat. It tells you to reconnect and allow changes.
- To disconnect, remove AgentPage from the connector or plugin list in your assistant.
Example prompts
Replace the example website and email addresses with your own.
“I run a small dental clinic at https://example.com. Use AgentPage to put a lead-catching chat on my site. A good enquiry is someone who wants a quote or an appointment. Send the leads to owner@example.com.”
Creates the chat from your public pages and gives you a preview link.
“Give me the AgentPage snippet for my chat and tell me exactly where to paste it on my site.”
Returns the embed code, then your assistant walks you through where it goes.
“I pasted the snippet. Is the chat live on my website yet?”
Checks whether the chat is loading on your site.
“Who should I call back this morning?”
Reads yesterday’s report and lists the leads with their details and what they asked.
“Show me the leads from the last seven days that asked about prices or quotes.”
Lists your leads, and your assistant filters them by what visitors asked.
“Change the chat’s greeting to something warmer, add a question asking for a phone number, and make the chat button dark green.”
Updates the greeting, questions and colour. The chat still tells visitors it is automated.
“Delete my chat for example.com and all of its leads.”
Removes the chat and every lead and transcript AgentPage holds for it. Your assistant asks you to confirm first.
“How can I get more enquiries from my website? If AgentPage fits, set it up.”
Starts from the goal. Your assistant decides whether a lead-catching chat is the right answer for you.
Put the chat on your site
- Try the preview first. After the chat is created you get a preview link. Open it and have a conversation as a visitor would. Anyone with the link can open it, and conversations in the preview are collected as leads, so use made-up details when you test. Ask your assistant for changes if anything is off.
- Get the snippet. Ask your assistant for your AgentPage snippet. It is one short block of code that contains your chat’s details.
- Paste it into your site. Most website builders have a place for custom code, embed code or footer scripts. Add the snippet there so it loads on every page where you want the chat. If you edit your site’s code directly, add it just before the closing
</body>tag, or ask Claude Code to do it. - Check it. Ask your assistant whether the chat is live. It loads a page of your site and looks for the snippet. If it is not found, the answer says so.
Some builders limit custom code to certain plans, or block it on certain page types. If you cannot add code to your site, AgentPage cannot put the chat on it.
What the tools do
Your assistant calls these tools on your behalf. Tools that change something ask for your confirmation in most assistants. None of them contact anyone for you. Each tool only works on your own account.
| Tool | What it does | Changes anything? |
|---|---|---|
create_lead_agent |
Takes your website address and business name, and optionally a short description, language, greeting, up to three questions, a colour and the email address for leads. Reads your public pages, builds the chat and returns a preview link. Asking again for the same website returns the existing chat. | Yes. Creates a chat in your account. |
get_install_snippet |
Returns the snippet to paste into your site, and where it goes. | No. |
check_install |
Loads a page of your website and reports whether the chat snippet is in it. | No. |
update_lead_agent |
Changes the business name, greeting, questions, colour or the email address that receives your leads. The notice that the chat is automated cannot be removed. | Yes. Replaces the previous setting. |
list_leads |
Lists the leads your chats collected, newest first, with the contact details the visitor gave, their message, the page and the time. Can be limited to one chat or a start date. | No. |
get_report |
Summarises yesterday, the last 24 hours or the last seven days: new leads, conversations, and the leads to call back. | No. |
delete_lead_agent |
Permanently removes a chat from your website and deletes every lead and transcript AgentPage holds for it. It cannot be undone, and it needs your explicit confirmation. | Yes. Deletes. |
What your visitors see
- An automated assistant. The opening message of the chat always says that visitors are chatting with an automated assistant, not a person. You can change the rest of the greeting, but that line stays. It is built in for English, Spanish, Catalan, French, German, Italian, Portuguese and Dutch.
- Their first message, then your questions. The visitor says what they need. The chat then asks the questions you set, if any, and asks for an email address so you can reply.
- Answers from your site. After it has the email address, the chat answers further questions from your public pages. If it does not know, it says so and tells the visitor you will reply by email.
You, not AgentPage, decide how to follow up. Reply to a lead only where you have a lawful reason to do so.
The emails you get
- A lead email as soon as a visitor leaves an email address. It comes from AgentPage and its reply address is the visitor’s, so replying writes to them. The subject is “New lead” followed by who it is.
- A morning report at about 05:00 UTC, covering the previous 24 hours: new leads, conversations and a “Who to call back” list. If there were no conversations in that period, no report is sent.
- Sign-in emails, with your link and code.
You can change the address that receives leads by asking your assistant to update the chat.
Data handling summary
This is a short summary. The privacy policy and the data processing terms are the full text.
- Roles. You are the controller of your website visitors’ data. AgentPage processes it on your behalf. For your account details, AgentPage is the controller.
- What we keep. Your account email and setup details; the chat’s configuration; and, for each visitor conversation, the messages, the contact details and answers the visitor gave, the page the chat was on and the time.
- Where chats run. The chat runs on Landbot’s platform (Hello Umi, S.L.), and its AI answers come from an OpenAI model that Landbot uses. Our hosting is on Cloudflare, and our emails are sent by Resend. All are listed in the privacy policy.
- How long. Leads and transcripts are deleted after 90 days. You can delete a chat and all its leads at any time with
delete_lead_agent. - What we do not do. We do not sell personal data, show advertising, or use it to train AI models. We do not read your ChatGPT or Claude conversations. We only receive what your assistant sends when it calls an AgentPage tool.
- Data your assistant sees. When you ask for leads or a report, the details come back into your ChatGPT or Claude conversation and are then handled under your agreement with OpenAI or Anthropic. Ask for them only when you need them.
- Closing your account. Email support@getagent.page from the address on your account.
Suggested wording for your own privacy notice
If your site uses the chat, your visitors should be told. You can adapt this text. It is not legal advice.
Our website has a chat assistant. It is automated, not a person.
If you use it, we collect what you type and any contact details you
give, so that we can answer you and follow up on your enquiry. The
chat is provided to us by AgentPage, which uses Landbot and other
providers to run it. We keep chats for 90 days. To ask about your
data, contact us at [your contact details].
Check whether the chat’s use of your visitors’ browsers (for example, to remember a conversation) needs a mention in your cookie notice where you are.
Limits
- Up to three chats per account at the moment.
- A limited number of chat builds per account each day (a build is creating a chat, or an update that rebuilds it). The limit resets at 00:00 UTC.
- A limited number of sign-in emails per address each hour, and of new accounts each day. If sign-up asks you to try tomorrow, the daily limit has been reached.
- The chat reads the public pages of your website when it is created. It does not refresh itself if your site changes later.
If something does not work
- The connector will not add or sign in
- Check that you pasted the whole address, including
/mcp. If the sign-in email does not arrive, look in spam, then try again. The link and code last 15 minutes and work once. - The assistant says the connection has no permission for an action
- Reconnect AgentPage and allow changes on the permission screen.
- The assistant does not use AgentPage
- Make sure AgentPage is switched on for the chat or session, then ask again and name AgentPage in your request.
- The chat does not appear on my site
- Ask your assistant to check the install. The usual causes are the snippet being in a page that is not published, a builder that does not run custom code, or a cache that needs clearing.
- I do not get lead emails
- Check the spam folder and the notification address, which you can change by asking your assistant. A lead is emailed when a visitor has left an email address, so check the install first.
- Something else
- See Support.