Give Replit Agent an email inbox

Replit Agent builds and deploys the app. The app almost always needs to send email, and sooner or later it needs to receive some too: a confirmation code, a customer reply, a webhook that arrives as a message rather than a POST.

Anjal gives both the agent and the app a real inbox, and on Replit there is no config file to edit.

Connect it

Open your project's Integrations page, scroll to MCP Servers for Replit Agent, and click Add MCP server.

• Base URL: https://mcp.anjal.app/mcp
• Leave the API key field empty.

Click Test & Save. Replit connects, and because our server supports OAuth dynamic client registration, it registers itself and sends you to Anjal to sign in and click Allow. No key is pasted into a field, and nothing secret ends up in your Repl.

Two details about Replit specifically that are worth knowing:

It is account-level, not per project. Add Anjal once and every project you build afterwards can reach it. That is convenient and it is also a scope decision: a connector added this way reaches your whole Anjal account from any Repl. If you would rather each project only see its own mail, use the scoped setup below.

Replit scans MCP traffic. Tool definitions and planned executions go through Replit's own security scanner before they run. That is a second pair of eyes on top of ours and it is a good thing; it is not a reason to skip scoping the key.

What Replit Agent gets

47 tools. The ones that matter while building an app:

What this is actually good for on Replit

Your app can receive email, not just send it. This is the thing most Replit apps are missing. create_webhook points at a route in your Repl, so an inbound message becomes an ordinary POST to your own code. Building a support tool, a ticketing system or anything that reads replies stops being an infrastructure project.

The agent can get itself past a signup wall. Wiring up a third-party API usually means creating an account on it. With an inbox, the agent registers, receives the confirmation, and reads the code out without you forwarding anything from your personal mail.

Test inbound without a public tunnel. An inbox is reachable from the internet by definition, so you can send it a message and watch your webhook fire against the deployed Repl.

Scoping it to one project

The account-level connector is convenient and broad. When a Repl should only reach its own mail, skip MCP for that project and put a workspace-scoped key in Replit Secrets instead, calling the REST API directly:

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

A wk_ key reaches one workspace and nothing else: it cannot list, read or send from any other, and cannot see that the others exist. Your plan gives you one workspace per inbox, so a workspace per project is usually affordable.

Before you point an agent at an inbox

Inbound mail is text a stranger wrote, and it is about to enter the context of an agent that writes and deploys code. Anjal screens every inbound message on the ingest path and quarantines what it judges hostile, so the agent does not read it, and an agent cannot release its own quarantine. We publish the architecture and not the rules. Read the honest limits: detection is advisory, and the rule that holds is to gate side-effects on the sender, in code.

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 Lovable
• Connect Anjal to Claude Code
• MCP server reference

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