Connect any AI agent
to Reloop.
The Reloop MCP server lets your AI agent do everything you can do in the Reloop dashboard. Add one URL, sign in with Reloop, and ask in plain language.
Works with your AI tools.
Setup guides for each client, plus any other client that speaks MCP.
How it works
No API key to create, paste or rotate. Your client signs in with Reloop.
Add the server URL
Paste the Reloop server URL into your client, or use its one-click install link.
https://reloop.sh/mcpSign in with Reloop
Your client opens the browser. Sign in and approve the workspace. OAuth handles the token, so there is no API key to copy or rotate.
Ask in plain language
Ask for what you need. The agent picks the right Reloop tool, runs it against your workspace and tells you what happened.
Everything the dashboard does
If you can do it in the Reloop dashboard, your agent can do it through MCP, on the same workspace and with the same data.
Emails
Send, batch, schedule and cancel email, and look up any message and its delivery status.
Contacts
Add and update contacts, manage custom properties, segments and topic subscriptions.
Campaigns
Draft a broadcast, pick the audience, schedule it or send it now.
Templates
Create and edit reusable templates, such as a password reset that matches your brand.
Automation
Build workflows that react to events, like a welcome series when someone signs up.
Inbox
Read inbound email and attachments, and follow threads in your agent inboxes.
Metrics & logs
Check delivery, bounce and open rates, and read the logs behind a change.
Domains
Add a sending domain, get the DNS records and check verification.
Webhooks & API keys
Create webhooks for delivery and inbound events, and manage API keys.
Ask your agent to…
Copy a prompt into your client once Reloop is connected.
Open source. Self-host it too.
The MCP server is part of the Reloop codebase. Running your own install? Connect the same clients to it, remote or over stdio.
Remote
Any client with Streamable HTTP support can use the /mcp endpoint of your own install, for example https://mail.example.com/mcp. It discovers your install's OAuth server and signs you in through the browser.
Local (stdio)
For clients that only launch local servers, run reloop-mcp with npx. Set RELOOP_API_KEY to a key from the API keys page and RELOOP_BASE_URL to the public URL of your install.
1{2 "mcpServers": {3 "reloop": {4 "command": "npx",5 "args": [6 "-y",7 "reloop-mcp"8 ],9 "env": {10 "RELOOP_API_KEY": "YOUR_API_KEY",11 "RELOOP_BASE_URL": "https://mail.example.com"12 }13 }14 }15}Connect your agent to Reloop.
Sign in once.
Pick your client in the dashboard and follow the steps. No API key to copy.
FAQ
Frequently asked questions.
A Model Context Protocol server at https://reloop.sh/mcp that connects AI clients to your Reloop workspace. It can do everything you can do in the Reloop dashboard: send email, manage contacts, run campaigns, edit templates, build automations, read the inbox, check metrics and logs, verify domains, and manage webhooks and API keys.
Not for the hosted server. Your client signs in with Reloop over OAuth: the browser opens, you approve the workspace, and the client receives a token scoped to it. API keys are only needed when you run reloop-mcp locally over stdio.
Claude Code, Claude (web and desktop), Cursor, VS Code with GitHub Copilot agent mode, and Codex have setup guides. Any client that supports remote MCP servers over Streamable HTTP can connect with the server URL, and clients that only launch local servers can run reloop-mcp over stdio.
Yes. Reloop is open source. Point remote clients at the /mcp endpoint of your own install, or run npx -y reloop-mcp with RELOOP_API_KEY set to a key from your install and RELOOP_BASE_URL set to its public URL.
Use the MCP server in chat and IDE clients that support MCP, where you ask in plain language. Use the Reloop CLI in shells, CI jobs and agents that run commands: every command takes --json and returns predictable exit codes.