Amply MCP connector
The Amply connector brings sending, verified domains, IP pools and delivery monitors into Claude, ChatGPT, Cursor and any MCP client, so your team can send email and check sending setup from a chat window while every action is logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Amply monitors flagged issues this week?
Working in Amply with Elaichi
-
List all Amply IP addresses
-
Get single Amply IP address by ID
-
List all Amply IP pools
How to connect Amply to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Amply MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Amply MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Amply MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Amply MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Amply MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Amply to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Amply through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Amply is logged.
-
Marketing
Send a one-off email without opening Amply
Ask for a message to go out through Amply to a customer or a test inbox, with the subject and body you dictate, and confirm it was accepted for delivery.
-
Engineering
Add a new sending domain and finish DNS
Create a verified domain in Amply, read back the exact DNS records that need to be published, then trigger validation once your domain provider has them in place.
-
Deliverability
Check which IP addresses are in which pool
List every dedicated IP address and IP pool in Amply, see how they are grouped, and move an address between pools when a warm-up plan calls for it.
-
Operations
Review every delivery monitor in one pass
Pull up all the monitors configured in Amply, see what each one watches, and update thresholds or names without clicking through each one.
-
IT
Audit verified domains before a rebrand
Get a full list of the domains Amply is allowed to send from, confirm which are validated, and retire the ones that no longer belong to the organization.
-
Support
Confirm the sending setup behind a complaint
When a customer says mail from your company looks suspicious, check in Amply which domain and IP pool their message would have used and whether that domain is verified.
Try asking
- “Which Amply monitors flagged issues this week?”
- “List the IP addresses in our production Amply pool.”
- “How many Amply emails went out yesterday?”
What connecting Amply gets you
6 screens from Elaichi, each doing one job for your Amply account.
Ask Elaichi to work across your apps.
Which Amply monitors flagged issues this week?
List the IP addresses in our production Amply pool.
How many Amply emails went out yesterday?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Amply emails in plain language.
Answers come from live Amply emails, IP pools and monitors, not stale exports.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Amply here.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
22 Amply tools are ready to call.
Emails, IP addresses, IP pools and monitors are covered without custom code.
Toolboxes
Every team gets its own Amply toolbox.
Curate one toolbox per team so each group sees only relevant Amply tools.
Shared connections
Teammates send through Amply without the credential.
See who connected each Amply account and how many teams and members share it.
Audit log
Every Amply call is on the record.
When, who, what happened, type and resource, appended for each Amply request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Amply digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch emails
Amply
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Amply
Queued
Automations
A schedule fires and Amply work finishes.
Fetch Amply emails, group them, draft a digest, approve, then post back.
Amply health
Refreshed 4 minutes ago · every 15 minutes · from the emails collection
Emails
1,284 ↓ 12%
Ip addresses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Emails created
Last 14 days
By team
Share of activity
Marketing 34%
Lifecycle EMEA 27%
Product notifications 21%
Support 18%
Collections and dashboards
Amply delivery numbers arrive before you ask.
Four metrics, 14 days of records created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Amply
All three can connect Amply to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Amply tools | Allow or restrict single Amply tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Amply call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Amply tools for your AI agents
22 tools are ready to call through Elaichi's MCP endpoint the moment you connect Amply, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Amply to Claude?
Connect Amply inside Elaichi first, which asks only for an Amply API key copied from your Amply account, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Amply is available in Claude, usually within a few minutes end to end.
Does Amply work with ChatGPT and Cursor as well as Claude?
Yes. Once Amply is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Amply once and every client your team uses picks it up.
What can an AI agent actually do with my Amply data?
With Amply connected, an agent can send an email through your Amply account, list and manage your verified sending domains, read the DNS records a new domain needs and kick off validation. It can also list, create, update and remove IP addresses, IP pools and delivery monitors. In practice that means asking in plain language to add a domain, check which pool an address sits in, or send a test message.
Does connecting Amply give the AI my whole sending account?
No. Every call to Amply runs under the API key of the person who connected it, so the agent can never do more in Amply than that person already can. Elaichi can then narrow that further, for example allowing reads on domains and monitors but not sending or deleting, and it never widens access beyond what the key itself allows.
Can I stop an agent from deleting or changing things in Amply?
Yes. Restrictions in Elaichi apply per action, so you can restrict deleting IP addresses, IP pools, monitors or verified domains in Amply while still allowing reads or sending. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or any other client cannot run it, whatever the prompt says.
What happens to an Amply connection when someone leaves?
Offboarding a person in Elaichi ends their access to Amply through every client at once, with no separate steps in Claude, ChatGPT, Cursor or Microsoft Copilot. If they had shared an Amply connection with a team, that connection keeps working for everyone else. Disconnecting Amply once in Elaichi removes it from every client at the same time.
Does the Amply MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Amply is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Amply?
Yes. Both let Claude, ChatGPT or Cursor use Amply. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Amply call.
How is Elaichi different from Composio for Amply?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Amply: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Amply in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot