---
title: "Connect Buildkite to Mercury - APIANT.ai"
description: "When \"New build\" fires in Buildkite, your agent runs \"Add customer\" in Mercury."
canonical: "https://apiant.ai/connect/buildkite-to-mercury"
---

# Connect Buildkite to Mercury

When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Add customer** in [Mercury](https://apiant.ai/connections/mercury). Describe the whole flow and it is built, tested on every scenario and kept running.

Buildkite **2** triggers Buildkite **12** actions Mercury **17** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Buildkite and Mercury to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Buildkite can start in Mercury

- When **New build** in Buildkite then **Add customer** in Mercury
- When **Build finished** in Buildkite 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 Buildkite and Mercury

## Triggers and actions 2 triggers · 29 actions

- Trigger

**Build finished**

Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).

- Trigger

**New build**

Triggers when a new build is scheduled in a Buildkite pipeline.

- Action

**Add annotation**

Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.

- Action

**Add build**

Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.

- Action

**Add pipeline**

Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.

- Action

**Cancel build**

Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build.

- Action

**Delete pipeline**

Permanently deletes a pipeline from your Buildkite organization.

- Action

**Get build**

Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.

- Action

**Get pipeline**

Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.

- Action

**List agents**

Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.

- Action

**List builds**

Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.

- Action

**List pipelines**

Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.

- Action

**Rebuild build**

Starts a new build that re-runs an existing build of a pipeline, and returns the new build.

- Action

**Update pipeline**

Updates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters.

- Action

**Add customer**

Creates a new Accounts Receivable customer in Mercury that you can invoice.

- Action

**Add internal transfer**

Transfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.

- Action

**Add recipient**

Creates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.

- Action

**Get invoice**

Returns the details of a Mercury invoice, including its customer, amount, status, dates and line items.

- Action

**Get organization**

Returns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.

- Action

**Get recipient**

Returns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.

- Action

**Get transaction**

Returns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.

- Action

**List accounts**

Returns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.

- Action

**List account statements**

Returns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.

- Action

**List categories**

Returns the organization's custom expense categories used to classify transactions.

- Action

**List customers**

Returns the accounts receivable customers on your Mercury account (up to 1000).

- Action

**List invoices**

Returns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.

- Action

**List recipients**

Returns the payment recipients saved in your Mercury account (up to 1000).

- Action

**List transactions**

Returns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.

- Action

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

- Action

**Update recipient**

Updates an existing payment recipient's name, contact details and payment routing information.

- Action

**Update transaction**

Updates the note and/or category of an existing Mercury transaction.

## Each app on its own

- [ **Buildkite** Buildkite is a platform for running fast, secure, and scalable continuous integration pipelines on your own...](https://apiant.ai/connections/buildkite)
- [ **Mercury** Mercury is an online financial platform that helps startups grow and manage their capital.](https://apiant.ai/connections/mercury)

Reviews

## What our customers say

## More from Buildkite

- [ **Buildkite to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/buildkite-to-hubspot)
- [ **Buildkite to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/buildkite-to-salesforce)
- [ **Buildkite to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/buildkite-to-slack)
- [ **Buildkite to Google Sheets** Google Sheets](https://apiant.ai/connect/buildkite-to-google-sheets)
- [ **Buildkite to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/buildkite-to-gmail)
- [ **Buildkite to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/buildkite-to-google-calendar)

## More into Mercury

- [ **HubSpot to Mercury** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-mercury)
- [ **Salesforce to Mercury** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-mercury)
- [ **Slack to Mercury** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-mercury)
- [ **Google Sheets to Mercury** Google Sheets](https://apiant.ai/connect/google-sheets-to-mercury)
- [ **Gmail to Mercury** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-mercury)
- [ **Google Calendar to Mercury** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-mercury)

Questions

## Buildkite and Mercury, answered

###

### What can start an automation from Buildkite?

Any of Buildkite's 2 triggers in the catalog, including New build and Build finished. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Mercury when something happens in Buildkite?

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

Mercury has no triggers in the catalog today, so automations start in Buildkite. 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 Buildkite 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 Buildkite 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.
