Integration
Connect Yandex to Mercury
When New file fires in Yandex, your agent runs Add customer in Mercury. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Yandex and Mercury to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Yandex can start in Mercury
When New file in Yandex
then Add customer in Mercury
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Yandex and Mercury
Triggers and actions 1 trigger · 29 actions
- New file
Triggers when a new file is uploaded to Yandex Disk.
- Add folder
Creates a new empty folder at the given path on Yandex Disk. The parent folder must already exist.
- Copy resource
Copies a file or folder on Yandex Disk to a new location and returns a link to the copy, or to the copy operation when Yandex performs it in the background.
- Delete resource
Deletes a file or folder on Yandex Disk, moving it to the Trash by default or removing it permanently.
- Get disk info
Returns general information about the connected user's Yandex Disk: total, used and trash space, file size limits, system folder paths and the disk owner.
- Get download link
Returns a temporary direct link for downloading a file stored on Yandex Disk.
- Get resource
Returns the details of a file or folder on Yandex Disk, such as its name, type, size, dates and custom properties. For a folder, the response also lists the items inside it.
- List files
Returns a flat list of every file on the user's Yandex Disk, optionally filtered by media type and sorted.
- List public resources
Returns the files and folders on your Yandex Disk that have been published with a public link.
- List recently uploaded files
Returns the files most recently uploaded to Yandex Disk, newest first, optionally filtered by media type.
- Move resource
Moves or renames a file or folder on Yandex Disk. Returns a link to the moved item, or to the background move operation when it runs asynchronously.
- Publish resource
Publishes a file or folder on Yandex Disk so it gets a public link, optionally with access settings such as a password or expiry. Returns a link to the published resource's metadata.
- Update resource
Adds or changes custom properties on a file or folder in Yandex Disk. Properties with the same name are overwritten, new ones are added, and a property set to null is removed.
- Add customer
Creates a new Accounts Receivable customer in Mercury that you can invoice.
- Add internal transfer
Transfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
- Add recipient
Creates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
- Get invoice
Returns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
- Get organization
Returns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
- Get recipient
Returns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
- Get transaction
Returns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
- List accounts
Returns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
- List account statements
Returns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
- List categories
Returns the organization's custom expense categories used to classify transactions.
- List customers
Returns the accounts receivable customers on your Mercury account (up to 1000).
- List invoices
Returns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
- List recipients
Returns the payment recipients saved in your Mercury account (up to 1000).
- List transactions
Returns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
- Send money
Sends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
- Update recipient
Updates an existing payment recipient's name, contact details and payment routing information.
- Update transaction
Updates the note and/or category of an existing Mercury transaction.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Yandex
Yandex to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Yandex to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Yandex to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Yandex to AnthropicAnthropic builds Claude, a family of large language models.
Yandex to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
Yandex to ElevenLabsElevenLabs is an AI audio research and deployment company.
More into Mercury
HubSpot to MercuryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to MercurySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to MercurySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to MercuryGoogle Sheets
Gmail to MercuryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MercuryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Yandex and Mercury, answered
What can start an automation from Yandex?
Any of Yandex's 1 trigger in the catalog, including New file. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mercury when something happens in Yandex?
Any of Mercury's 17 actions, including Send money, Update recipient, Update transaction and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mercury to Yandex?
Mercury has no triggers in the catalog today, so automations start in Yandex. If you need the other direction, ask: your agent reads Mercury's API documentation and adds it.
Do I have to build a connector for Yandex or Mercury?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Yandex and Mercury without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.