Use Meerlume from your AI assistant
Connect Meerlume to Claude, ChatGPT, Cursor or another assistant that supports MCP, and build bots, run your calendar and look things up by asking.
Use this guide when you would rather ask the assistant you already use than click through the dashboard. Meerlume has an MCP server, the standard way AI assistants connect to other apps. Add it to your assistant, sign in to Meerlume and choose Allow, and the assistant can do most of what Lume, the assistant built into your dashboard, can do. It is included on every plan, Free too.
See every assistantBefore you start
- A Meerlume account. You sign in to it while connecting, so make one first if you have none.
- An assistant that supports remote MCP servers: Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Gemini CLI and many others do.
- The server's address:
https://mcp.meerlume.com/mcp. There is no API key: you sign in instead.
Let your agent do it
Agents that can set themselves up (Claude Code, Codex and similar) only need this line: Set up Meerlume - https://meerlume.com/setup.md. They read the instructions and connect, and ask you to sign in.
Connect Claude
On claude.ai and in the Claude apps, on every Claude plan. Free allows one custom connector.
- Open Customize, then Connectors.
- Choose + Add, then Add custom connector.
- Name it Meerlume, paste https://mcp.meerlume.com/mcp as the URL, choose Continue, then Add.
- Choose Connect, sign in to Meerlume and choose Allow. On Team and Enterprise, an owner adds it under Organization settings, Connectors, and each person connects it from Customize, Connectors.
Connect ChatGPT
Uses developer mode. Which ChatGPT plans have it, and whether it can make changes there, is up to OpenAI.
- Open Settings, then Apps & Connectors, then Advanced settings, and turn on Developer mode.
- Back in Apps & Connectors, choose Create.
- Name it Meerlume, paste https://mcp.meerlume.com/mcp as the URL and choose OAuth.
- Tick I trust this application, choose Create, sign in to Meerlume and choose Allow.
Connect Cursor
Adds Meerlume to Cursor's MCP servers.
- Choose Add to Cursor and confirm in Cursor.
- When Cursor asks, sign in to Meerlume and choose Allow.
The Add to Cursor button is on the Use Meerlume from your AI assistant page.
Connect VS Code
For Copilot's agent mode.
- Choose Add to VS Code and confirm the install.
- Start the server when VS Code offers to, sign in to Meerlume and choose Allow.
The Add to VS Code button is on the Use Meerlume from your AI assistant page.
Connect Claude Code
Run it in a terminal, or paste it into any Claude Code session and Claude runs it for you.
The command: claude mcp add --transport http meerlume --scope user https://mcp.meerlume.com/mcp
- Add it with the command. --scope user makes it available in every project.
- Type /mcp, choose meerlume and sign in to Meerlume. From a terminal: claude mcp login meerlume.
Connect Codex
Run it in a terminal, or paste it into a Codex session. The ChatGPT desktop app and the Codex IDE extension share it.
The command: codex mcp add meerlume --url https://mcp.meerlume.com/mcp
- Add it with the command.
- Run codex mcp login meerlume and sign in to Meerlume.
Connect Gemini CLI
Run it in a terminal, or paste it into a Gemini CLI session.
The command: gemini mcp add --transport http -s user meerlume https://mcp.meerlume.com/mcp
- Add it with the command. -s user makes it available in every project.
- Type /mcp auth meerlume and sign in to Meerlume.
Connect any other assistant
Anything that supports remote MCP servers: Windsurf, Antigravity, Zed and more.
- Add a remote (HTTP) MCP server with the URL https://mcp.meerlume.com/mcp. In a JSON settings file that is "meerlume": { "url": "https://mcp.meerlume.com/mcp" } under mcpServers; Windsurf and Antigravity call the field serverUrl.
- Sign in to Meerlume when it asks, and choose Allow. There is no key to copy.
What to ask
Ask in your own words and your own language. A few to start with:
- “Build a bot for my barbershop: haircuts take 30 minutes and cost €25, beard trims 15 minutes and €12, and we're open Tuesday to Saturday, 10 to 7.”
- “What bookings do I have tomorrow?”
- “Close the shop from 24 to 26 December.”
- “Make the welcome message friendlier, then publish the bot.”
- “Show me this week's new enquiries.”
- “I want to take bookings on WhatsApp too.”
Your assistant can look up your account, bots, conversations, contacts, bookings and settings. It can build a bot or change what one says, set up services, staff and opening hours, publish or unpublish, add website chat and choose your notifications. It cannot delete a bot or your account, message your customers or change your plan.
Connecting a channel
Ask to connect WhatsApp, Telegram, Messenger, Instagram, Stripe, Slack or Notion and your assistant gives you a link. It opens the right page in Meerlume, where you sign in with Meta or confirm in Telegram yourself. Your assistant never sees what you enter there.
Stay in control
- The page where you choose Allow names the assistant and whether it asks to read only, or to read and change.
- It works in your own workspace, the one your bots are in.
- Reading what customers wrote in a conversation is off until you switch on Read what customers wrote in Settings. Without it, your assistant sees who wrote and when, not the messages.
- A change to what a bot says is saved as unpublished changes. Customers see nothing new until you publish.
- What your assistant looks up is passed to it, and so to the company that runs it, under your own terms with them.
Disconnect any time
Open Settings in Meerlume and choose Disconnect next to the assistant under Connected apps. It loses access straight away.
Related guides
Continue with the next part of the setup once this step is stable.
Create your first bot
Start from a plain-language description or a template, generate a first draft, and understand what guests can do before signing up.
Set up the calendar
Configure timezone, hours, services, and resources so your bot can offer real bookings instead of just collecting requests.
Preview drafts and publish
Test the conversation before it goes live, understand the draft/live split, and publish only when the workflow is ready.