---
title: "Connect Buildkite to Meisterplan - APIANT.ai"
description: "When \"New build\" fires in Buildkite, your agent runs \"Create or Update Tasks of a Project's Tool Link\" in Meisterplan."
canonical: "https://apiant.ai/connect/buildkite-to-meisterplan"
---

# Connect Buildkite to Meisterplan

When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Create or Update Tasks of a Project's Tool Link** in [Meisterplan](https://apiant.ai/connections/meisterplan). Describe the whole flow and it is built, tested on every scenario and kept running.

Buildkite **2** triggers Buildkite **12** actions Meisterplan **19** 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 Meisterplan 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 Meisterplan

- When **New build** in Buildkite then **Create or Update Tasks of a Project's Tool Link** in Meisterplan
- When **Build finished** in Buildkite then **Create or Update a Project's Tool Link** in Meisterplan

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 Meisterplan

## Triggers and actions 2 triggers · 31 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

**Create or Update Actual Time Worked**

Records the hours a resource or role actually worked on a project for a given date, updating the existing entry if one is already there. Returns the stored entry.

- Action

**Create or Update Allocation**

Allocates a resource or role to a project for a date range, updating the existing allocation if one is already there. Returns the allocation with its resulting segments.

- Action

**Create or Update a Project's Tool Link**

Links a Meisterplan project to the matching project in a task management tool, updating the link if one already exists. Returns the stored link.

- Action

**Create or Update Resource Absence**

Records an absence for a resource over a date range, so the time is taken out of their availability. Returns the stored absence.

- Action

**Create or Update Tasks of a Project's Tool Link**

Pushes a task from a linked task management tool onto a Meisterplan project, updating it if the task key is already there.

- Action

**Create Project**

Creates a project in a Meisterplan scenario, including its dates, budgets and custom fields. Returns the new project.

- Action

**Create Resource**

Adds a person to the Meisterplan resource pool, with their role, calendar, cost rate and org placement. Returns the new resource.

- Action

**Create Role**

Creates a role in Meisterplan that resources can be assigned to and projects can be allocated against. Returns the new role.

- Action

**Find a Resource or Role**

Returns the resources and roles whose key, name or email matches the text you supply. Meisterplan has no server-side search on these collections, so the match is made after fetching them.

- Action

**Find a Team, Resource or Role**

Returns the teams, resources and roles whose name, key or email matches the text you supply. Meisterplan has no server-side search on these collections, so the match is made after fetching them.

- Action

**Find Project by Key**

Returns the project in a scenario that carries the project key you supply. Meisterplan has no server-side project search, so the match is made after fetching the scenario's projects.

- Action

**Find Project by Name**

Returns the projects in a scenario whose name contains the text you supply. Meisterplan has no server-side project search, so the match is made after fetching the scenario's projects.

- Action

**Find Resource by Email**

Returns the resource whose email address matches the one you supply. Meisterplan has no server-side resource search, so the match is made after fetching the resource pool.

- Action

**Find Resource by Key**

Returns the resource carrying the resource key you supply. Meisterplan has no server-side resource search, so the match is made after fetching the resource pool.

- Action

**Find Role by Name**

Returns the role carrying the name you supply. Meisterplan has no server-side role search, so the match is made after fetching the roles.

- Action

**Find Task by Key**

Returns the task on a project's tool link that carries the task key you supply. Meisterplan has no server-side task search, so the match is made after fetching the project's tasks.

- Action

**Update Project**

Updates a project in a Meisterplan scenario — its dates, budgets, status and custom fields. Only the values supplied are changed. Returns the updated project.

- Action

**Update Resource**

Updates a person in the Meisterplan resource pool — their name, role, calendar, cost rate and org placement. Only the values supplied are changed. Returns the updated resource.

- Action

**Update Role**

Updates a role in Meisterplan — its name, cost rate and org placement. Only the values supplied are changed. Returns the updated role.

## 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)
- [ **Meisterplan** Meisterplan is a project portfolio management tool that focuses on resource management at the portfolio...](https://apiant.ai/connections/meisterplan)

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 Meisterplan

- [ **PyPI to Meisterplan** Package metadata, release history and download files for any Python package published on the Python Package...](https://apiant.ai/connect/pypi-to-meisterplan)
- [ **HubSpot to Meisterplan** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-meisterplan)
- [ **Salesforce to Meisterplan** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-meisterplan)
- [ **Slack to Meisterplan** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-meisterplan)
- [ **Google Sheets to Meisterplan** Google Sheets](https://apiant.ai/connect/google-sheets-to-meisterplan)
- [ **Gmail to Meisterplan** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-meisterplan)

Questions

## Buildkite and Meisterplan, 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 Meisterplan when something happens in Buildkite?

Any of Meisterplan's 19 actions, including Create or Update Actual Time Worked, Create or Update Allocation, Create or Update a Project's Tool Link and Create or Update Resource Absence. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Meisterplan to Buildkite?

Meisterplan has no triggers in the catalog today, so automations start in Buildkite. If you need the other direction, ask: your agent reads Meisterplan's API documentation and adds it.

###

### Do I have to build a connector for Buildkite or Meisterplan?

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