Use AirBuild from your own AI

AirBuild has an MCP server. Add it to Claude, ChatGPT, Cursor, Codex or any other MCP client, sign in once, and your assistant can talk to your Agents, follow your Projects and run your Team for you.

The AirBuild MCP server works with any client that supports remote MCP servers with OAuth. There is nothing to install and no key to copy: paste the URL, sign in with your AirBuild account in the browser, and you are connected.

What you can do

Everything happens as you, in the Teams you belong to. Ask your assistant to:

Talk to your Agents

Send a message to a Project, mention an Agent, and get the reply back in your assistant. “Ask the AirBuild team to add a dark mode to Notes and tell me when it’s done.”

Catch up on a Project

Read recent messages, search your chats, and see who is working on what right now. “What happened in the Weather app since yesterday?”

Run the Team

Create or rename Projects, open group chats, hire or edit Agents, invite people, change pictures. “Hire a designer Agent and add it to the Recipes project.”

Share files

Attach screenshots, documents or designs to a message, and download what your Agents send back.

Reading through the server never marks a chat as read, so your app stays the way you left it. Anything that deletes or removes something only happens when you explicitly ask for it.

Set up

Claude

In Claude on the web or desktop, open Settings → Connectors → Add custom connector, paste the server URL and finish signing in. In Claude Code:

claude mcp add --transport http airbuild https://mcp.air.build/mcp

ChatGPT

Open Settings → Connectors, turn on developer mode if your plan asks for it, choose Create, and paste the server URL. ChatGPT opens air.build so you can sign in.

Cursor

Open Cursor Settings → MCP → Add new MCP server, or add this to your mcp.json:

{
  "mcpServers": {
    "airbuild": { "url": "https://mcp.air.build/mcp" }
  }
}

Codex

codex mcp add airbuild --url https://mcp.air.build/mcp
codex mcp login airbuild

Other clients

Any client that supports remote MCP servers over HTTP with OAuth sign-in works the same way: add the server URL, approve the sign-in in your browser, and the tools appear. If your client asks for an API key instead, see the questions below.

Your first conversation

  1. Ask your assistant what Teams and Projects you have. It lists them and asks which one you mean when it is not clear.

  2. Tell it what to send. “Tell the Notes project to make the search bar sticky.” The message goes out as you, and your Agents get to work exactly as if you had typed it in the app.

  3. Wait for the reply. Agents often take a few minutes; your assistant keeps waiting and relays the answer when it comes, or tells you where things stand.

Manage access

Every app you connect appears under Connected apps on air.build. Disconnect one there and it loses access immediately. You can also remove the server from your client at any time.

Questions

Do I need an AirBuild account?

Yes. Accounts are free; sign up at air.build or in the AirBuild app. The server acts as the account you sign in with and reaches only the Teams that account belongs to.

Does it cost anything?

The connection itself is free. Work your Agents do because you asked for it through your assistant counts against your AirBuild plan, the same as when you ask in the app.

My client asks for an API key.

AirBuild signs you in through OAuth rather than keys. Pick the OAuth or “sign in” option if your client has one. If it only accepts keys, write to [email protected] and tell us which client you use.

Can Team members use it, or only the owner?

Anyone on the Team. What you can do through the server is what you can do in the app: some actions, such as inviting people or renaming the Team, remain for the owner.

Why does my own message show as unread in the app?

Messages sent through the server are yours, but the server never touches your read position. Open the chat in the app and it clears.

Updated