# 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.

Source: https://elaichi.ai/connectors/amply/

## Facts

| | |
| --- | --- |
| Application | Amply |
| Category | Email |
| AI tools | 22 |
| Authentication | Connects with an API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Amply is connected

- Which Amply monitors flagged issues this week?
- List the IP addresses in our production Amply pool.
- How many Amply emails went out yesterday?

## Connect Amply in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Amply.
2. Optionally set Share with, then press Connect.
3. Paste an Amply API key. One person generates a token in Amply and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Amply tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Connect Amply to Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Connect Amply to ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Connect Amply to Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Amply to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Amply tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Amply through Elaichi

### Send a one-off email without opening Amply

Marketing. 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.

### Add a new sending domain and finish DNS

Engineering. 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.

### Check which IP addresses are in which pool

Deliverability. 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.

### Review every delivery monitor in one pass

Operations. Pull up all the monitors configured in Amply, see what each one watches, and update thresholds or names without clicking through each one.

### Audit verified domains before a rebrand

IT. 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.

### Confirm the sending setup behind a complaint

Support. 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.

## Frequently asked questions

### 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, 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 my team share one Amply connection?

Yes. One person connects Amply with their API key and shares the connection with a team in Elaichi, and nobody else on the team ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so every send, domain change or pool update in Amply is recorded against the person who asked for it.

### Can I stop an agent from deleting or changing things in Amply?

Yes. Restrictions in Elaichi apply per action, so you can block deleting IP addresses, IP pools, monitors or verified domains in Amply while still allowing reads or sending. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client at all, so no prompt, however worded, can reach it.

### 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 or Cursor. 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.

## All 22 Amply tools

Every tool below is callable through https://api.elaichi.ai/mcp once Amply is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Amply email** (Create). Send an email via amply. Supply `from`, `personalizations` (with recipient `to` addresses), and either `content` or a `template` UUID to compose the message. Returns an empty JSON object on success.
- **List all Amply IP addresses** (List). List all IP addresses in amply. Returns an array of IP address objects including id, public_ip, enabled, status, rdns, and associated ip_pools.
- **Get single Amply IP address by ID** (Get). Get a single amply IP address by id. Returns: id, public_ip, uuid, enabled, rdns, status, created_at, and ip_pools. Required: id.
- **Update a Amply IP address by ID** (Update). Update an amply IP address by id. Returns the updated IP address object including id, public_ip, enabled, rdns, status, and ip_pools. Required: id.
- **Delete a Amply IP address by ID** (Delete). Delete an amply IP address by id. Returns an empty 200 response on success. Required: id.
- **List all Amply IP pools** (List). List all IP pools in amply. Returns an array of pool objects including id, name, uuid, status, and created_at.
- **Get single Amply IP pool by ID** (Get). Get a single amply IP pool by id. Returns the pool object including id, name, uuid, status, created_at, and ip_addresses. Required: id.
- **Create a Amply IP pool** (Create). Create a new IP pool in amply. Returns the created pool object including id, name, uuid, status, and created_at.
- **Update a Amply IP pool by ID** (Update). Update an existing amply IP pool by id. Returns the updated pool object including id, name, uuid, status, and created_at. Required: id.
- **Delete a Amply IP pool by ID** (Delete). Delete an amply IP pool by id. Returns an empty response on success. Required: id.
- **List all Amply monitors** (List). List all monitors in amply. Returns an array of monitor objects including id, name, type, detection_method, detection_type, notifications, and alert_conditions.
- **Get single Amply monitor by ID** (Get). Get a single amply monitor by id. Returns the full monitor object including id, name, type, detection_method, detection_type, notifications, alert_conditions, and created_at. Required: id.
- **Create a Amply monitor** (Create). Create a new monitor in amply. Returns the created monitor object including id, name, type, detection_method, detection_type, alert_conditions, and created_at.
- **Update a Amply monitor by ID** (Update). Update an existing amply monitor by id. Returns the updated monitor object including id, name, type, detection_method, alert_conditions, and created_at. Required: id.
- **Delete a Amply monitor by ID** (Delete). Delete an amply monitor by id. Returns an empty response on success. Required: id.
- **List all Amply verified domains** (List). List all verified domains in amply. Returns an array of domain objects including id, name, deliverability_strategy, status, and created_at for each entry.
- **Get single Amply verified domain by ID** (Get). Get the DNS challenge records for an amply verified domain by id. Returns: spf, dkim, whitelabel, and shared values representing the CNAME and TXT records that must be created to complete domain verification. Required: id.
- **Create a Amply verified domain** (Create). Create a verified domain in amply. Returns the created domain object including id, name, deliverability_strategy, status, and created_at. Required: name.
- **Update a Amply verified domain by ID** (Update). Update a verified domain's deliverability strategy in amply by id. Returns the updated domain object including id, name, and status. Required: id.
- **Delete a Amply verified domain by ID** (Delete). Delete a verified domain in amply by id. Returns an empty response on success. Required: id.
- **Get single Amply verified domain DNS challenge by ID** (Get). Get the DNS challenge details for a verified domain in Amply. Required: verified_domain_id.
- **Create a Amply verified domain validation** (Create). Trigger validation for a verified domain in amply. Initiates the validation process for the specified domain. Required: verified_domain_id.