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.

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.

Connect on Elaichi How to connect

How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
One address. https://api.elaichi.ai/mcp, the same for every user.
Their own access. An agent never gets more than the person it acts for.

22 tools

How to connect

How to connect Amply to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Amply once

Open Connections, choose Add connection, and pick Amply.
Optionally set Share with to give a team access, then press Connect.
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.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

amply

All categories

Amply

ElasticEmail

Flexmail

Gmail

Mailchimp

Mailtrap

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

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

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.

Connect Amply on Elaichi See pricing

Use cases

What teams do with Amply through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

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?”

See all 22 Amply tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Amply, by what to check
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	$15 per user per month.	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.

AI tools

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.

See it in Elaichi

What connecting Amply gets you

6 screens from the product, each doing one job for your Amply account.

The agent

Ask about Amply emails in plain language.

Answers come from live Amply emails, IP pools and monitors, not stale exports.

emails
ip addresses
ip pools
monitors

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

MCP clients

Claude, ChatGPT and Cursor reach Amply here.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

22 Amply tools are ready to call.

Emails, IP addresses, IP pools and monitors are covered without custom code.

Create a Amply email
List all Amply IP addresses
Get single Amply IP address by ID
Update a Amply IP address by ID

ElaichiTools

Tool	Action	Description
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.

Toolboxes

Every team gets its own Amply toolbox.

Curate one toolbox per team so each group sees only relevant Amply tools.

Marketing
Lifecycle
Deliverability
Platform

ElaichiToolboxes

Name	Source template	Tools	Created
Marketing toolbox Amply · campaign emails	Amply starter	18	Mar 4, 2026
Lifecycle toolbox Amply · transactional emails	—	9	Mar 2, 2026
Deliverability toolbox Amply · IP pools and monitors	—	24	Feb 27, 2026
Platform toolbox Amply · IP addresses and routing	Amply starter	6	Feb 19, 2026
Support toolbox Amply · email delivery lookups	—	31	Jan 30, 2026
Growth toolbox Amply · send volume and reporting	—	12	Jan 22, 2026

Shared connections

Teammates send through Amply without the credential.

See who connected each Amply account and how many teams and members share it.

Marketing
Lifecycle EMEA
Product notifications
Support

ElaichiConnections

Connection	Scope	Status	Access
AM Amply (Marketing) Connected by Emily Carter	Personal	• Active	1 team · 6 members
AM Amply (Lifecycle EMEA) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
AM Amply (Product notifications) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
AM Amply (Support) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
AM Amply (Deliverability) Connected by Ryan Hayes	Personal	• Active	Not shared
AM Amply (Billing alerts) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every Amply call is on the record.

When, who, what happened, type and resource, appended for each Amply request.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	Amply Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Amply Emails Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Amply Emails List	Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and Amply work finishes.

Fetch Amply emails, group them, draft a digest, approve, then post back.

Amply digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

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 Michael Brennan

Approve Deny
Post the digest

Amply

Queued

Collections and dashboards

Amply delivery numbers arrive before you ask.

Four metrics, 14 days of records created and a team breakdown, computed on schedule.

Amply health

Refreshed 4 minutes ago · every 15 minutes · from the emails collection

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

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

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect Amply Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.