Amply
Connect Amply to Elaichi and hand every teammate a governed MCP endpoint — 22 tools ready to call from Claude, Cursor, or any MCP client, clamped by roles, restrictions, and an audit log.
AI tools
Amply tools for your AI agents
22 tools are ready to mint as an MCP endpoint the moment you connect Amply — governed by the same roles, restrictions, and audit log as everything else in Elaichi.
create_a_amply_email
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 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 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 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 an amply IP address by id. Returns an empty 200 response on success. Required: id.
list_all_amply_ip_pools
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 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 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 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 an amply IP pool by id. Returns an empty response on success. Required: id.
list_all_amply_monitors
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 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 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 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 an amply monitor by id. Returns an empty response on success. Required: id.
list_all_amply_verified_domains
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 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 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 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 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 the DNS challenge details for a verified domain in Amply. Required: verified_domain_id.
create_a_amply_verified_domain_validation
Trigger validation for a verified domain in amply. Initiates the validation process for the specified domain. Required: verified_domain_id.
How it works
From Amply account to governed MCP endpoint
Connect
Link a Amply account through Elaichi's hosted connect flow. Credentials are vaulted — nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Amply tools are exposed, rename them, or freeze arguments.
Mint
Mint a personal MCP endpoint on that toolbox and paste it into Claude, Cursor, or any MCP client — governed by roles, restrictions, and audit logs.
Give every teammate a governed MCP server
Start a 14-day Gold trial — connect a product, curate a toolbox, and paste an endpoint into Claude or Cursor in minutes.