Monitor your Lovable app

Add your Lovable app's URL to Lampwick for uptime, SSL, domain and DNS checks without code, and connect Lovable's chat to Lampwick over MCP.

Updated View as Markdown

Paste your published Lovable app's address into Lampwick and it checks the app from outside Lovable, with alerts on your phone. Connect Lovable's chat to Lampwick and it can read what Lampwick found, and fix it.

Where your Lovable app runs

When you publish, Lovable hosts your app at an address ending in lovable.app. On a paid plan you can connect your own domain under Project → Settings → Domains, and Lovable sets up its SSL certificate (Lovable docs: custom domain, checked 8 Nov 2026).

Monitor the address your visitors use. On your own domain, its renewal and DNS are your job, and Lampwick watches both.

Lovable's own Project monitoring (beta, Pro plans and up) reads your code and visitor errors once a day (Lovable docs, checked 8 Nov 2026). Lampwick checks from outside Lovable and doesn't read code. Use both.

Monitor it without code

  1. Create a Lampwick account, confirm your email, and create a project named after your app.
  2. Click Uptime in the sidebar. Under Add monitor, paste your app's address, such as https://myapp.com, and click Add monitor.
  3. The monitor shows Pending, then Up. SSL, domain and DNS checks are on already.

Every click, plus the status page: the overview.

On Lovable apps created before 13 May 2026, Lampwick's site crawl finds few links: those apps build pages with JavaScript and send finished pages only to verified crawlers such as search engines (Lovable docs: SEO, checked 8 Nov 2026). Newer apps send them to everyone.

Connect Lovable to Lampwick

MCP is a standard way for an AI agent to use another app's tools; Lovable calls these Connectors. Connected, Lovable can look up your monitors, expiry dates and broken links.

Add Lampwick in Lovable (Lovable docs: custom MCP, checked 9 Nov 2026):

  1. Open Connectors, click Add custom at the top right, and choose MCP server. If it's grayed out, a workspace admin has turned custom MCP servers off.
  2. Server name: lampwick. Server URL: https://app.lampwick.dev/mcp.
  3. For authentication, keep OAuth and click Add & authorize.
  4. Lampwick opens. Log in, choose Read-only (recommended) and click Connect.

Read-only lets Lovable look at everything in Lampwick but change nothing. Disconnect it any time under Account & security → Connected apps. If Lovable can't connect this way, use a read-only token instead (connect with a personal token).

Lovable uses the connection only in your chat, never in your published app.

Check that it works

In your project's chat, ask "Which Lampwick projects can you see?". Lovable should name your project. If it isn't authorized, remove the server in Connectors and add it again. Then try:

  • "Is my Lampwick monitor up, and when does my SSL certificate expire?"
  • "Which broken links did Lampwick's last crawl find? Fix the ones in this project."

Errors inside your app, such as a button that throws, reach Lampwick once you add the browser error snippet. Paste the prompt from your project's Settings → Browser errors into Lovable's chat, and it adds one line to your app.

Start free, or read the MCP reference.