mercury_add_recipient
Add a payment recipient to Mercury for ACH, wire, or check transfers. Use to onboard vendors or contractors before sending money. Returns recipient ID needed by send-money tools. Idempotent via idempotency key.
Instructions
Add a new payment recipient (a counterparty you can later send money to via ACH/wire/check).
USE WHEN: onboarding a new vendor, contractor, or other payee before sending money. The returned id is what mercury_send_money and mercury_request_send_money expect as recipientId.
DO NOT USE: for AR customers (use mercury_create_customer — recipients receive money, customers pay invoices). Mercury enforces strict KYC/banking validation on bank fields — invalid routing numbers or account numbers are rejected at create time.
SIDE EFFECTS: writes a new recipient to Mercury. Persistent. Idempotent via idempotencyKey — the MCP auto-generates one if not provided, so repeated calls with the same generated key would not duplicate; pass an explicit idempotencyKey to make this stable across retries you control.
RETURNS: { id, name, status, defaultPaymentMethod, ... } — keep id for the send-money tools.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Recipient legal name | |
| emails | Yes | List of email addresses | |
| paymentMethod | Yes | Payment method to send to this recipient | |
| defaultPaymentMethod | No | Default payment method | |
| electronicRoutingInfo | No | Bank account info for ACH/wire | |
| idempotencyKey | No | Unique key to prevent duplicates |