Give Lovable an email inbox

Lovable generates the app. Almost every app it generates eventually needs email, and "eventually" is usually the moment you want a signup confirmation, a password reset or a contact form that actually reaches someone.

Anjal is a custom MCP server you add once as a chat connector.

Connect it

Open Connectors, go to the Chat connectors tab, and click New MCP server.

• Name: Anjal
• MCP endpoint URL: https://mcp.anjal.app/mcp
• Authentication: leave it on OAuth, which is Lovable's default when the server supports it. Ours does.

Lovable registers itself, sends you to Anjal to sign in and click Allow, and the tools appear. There is no API key to paste, which matters more here than in an editor: a key pasted into a generated app has a habit of ending up in the repo.

Chat connectors are enabled by default on every plan, including Enterprise. The only Enterprise-gated part is Lovable's static-IP option for custom MCP servers, which you do not need for us: we do not require IP allowlisting.

What Lovable gets

47 tools. Building an app, these are the ones that come up:

Why this is worth doing at generation time

The generated app gets working email instead of a TODO. Lovable can create the inbox, register the webhook and wire the send call while it is building, so the app that comes out the other side already sends and receives. That is the difference between a prototype and something you can put in front of a user.

Email is a hard thing to add later. SPF, DKIM, DMARC, a sending domain with a reputation, bounce handling. Starting from an inbox that already has all of that is a much better position than bolting an ESP on after launch and discovering your mail goes to spam.

A chat connector is also a research tool. Lovable can look things up in your Anjal account while it builds, so "what does the payload of an inbound message look like" is answered from your real data rather than guessed.

Scoping the app, not just the connector

The connector is for Lovable itself. For the deployed app, use a key rather than MCP, and scope it:

curl -X POST https://anjal.app/v1/inboxes/$INBOX/send \
  -H "X-API-Key: $ANJAL_KEY" -H "Content-Type: application/json" \
  -d '{"to":"user@example.com","subject":"Confirm your email","plainBody":"..."}'

Use a workspace-scoped wk_ key in the app's environment, never your tenant master key. It reaches one workspace and cannot see that any others exist, so a key that leaks out of a generated app costs you that workspace and nothing more. Your plan gives you one workspace per inbox, so an app per workspace is usually affordable.

Before the app reads mail from strangers

Anything a user emails your app is attacker-controlled text, and if you feed it to a model it is an injection surface. Anjal screens every inbound message on the ingest path and quarantines what it judges hostile before an agent can read it; an agent cannot release its own quarantine. We publish the architecture and not the rules. Agent safety is honest about the limits: detection is advisory, and gating side-effects on the sender in code is the part that actually holds.

Cost

Starter is $5/month for 2 inboxes and 6,000 emails. Developer is $15/month for 10 inboxes and 20,000 emails. Extra inboxes are $2/month each. 7-day trial.

Next

• Connect Anjal to Replit
• Connect Anjal to Cursor
• MCP server reference

Setup verified against Lovable's MCP servers documentation on 2026-09-28.