Integration
Connect SQL Server to Mercury
When New or Updated Row fires in SQL Server, 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 SQL Server 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 SQL Server can start in Mercury
When New or Updated Row in SQL Server
then Add customer in Mercury
When New Row in SQL Server
then Get invoice 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 SQL Server and Mercury
Triggers and actions 4 triggers · 24 actions
Trigger
New or Updated RowTriggers when a new row is added or modified.
Trigger
New or Updated Row (Custom Query)Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.
Trigger
New RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected SQL Server database.
Action
Add RowAdd one row to a table on the connected SQL Server database.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFind the first row in a table whose chosen column matches a value.
Action
Find Rows via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns every row it matches.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
Action
Run Custom StatementRuns a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
Action
Update RowChange column values on every row of a table whose chosen column matches a value.
Action
Add customerCreates a new Accounts Receivable customer in Mercury that you can invoice.
Action
Add internal transferTransfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
Action
Add recipientCreates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
Action
Get invoiceReturns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
Action
Get organizationReturns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
Action
Get recipientReturns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
Action
Get transactionReturns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
Action
List accountsReturns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
Action
List account statementsReturns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
Action
List categoriesReturns the organization's custom expense categories used to classify transactions.
Action
List customersReturns the accounts receivable customers on your Mercury account (up to 1000).
Action
List invoicesReturns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
Action
List recipientsReturns the payment recipients saved in your Mercury account (up to 1000).
Action
List transactionsReturns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
Action
Send moneySends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
Action
Update recipientUpdates an existing payment recipient's name, contact details and payment routing information.
Action
Update transactionUpdates 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 SQL Server
SQL Server to StripeStripe is a payment processing platform for online businesses.
SQL Server to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
SQL Server to JIRAAtlassian JIRA Cloud — issue tracking and project management.
SQL Server to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
SQL Server to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
SQL Server to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
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
SQL Server and Mercury, answered
What can start an automation from SQL Server?
Any of SQL Server's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mercury when something happens in SQL Server?
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 SQL Server?
Mercury has no triggers in the catalog today, so automations start in SQL Server. 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 SQL Server 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 SQL Server 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.