Connect Antigravity to Mangobeds with MCP

Antigravity, Google’s agentic development environment, can read your live Mangobeds data and answer questions about it without you leaving your work. An Antigravity MCP connection uses your API key, because Antigravity runs on your own computer and can send a header with each request. For the background on MCP, or if you use a different tool, start with Connect Mangobeds to AI tools with MCP.

Before you start

In Mangobeds, go to Apps > MCP and pick Antigravity. The block shown there already has your API key in it, so copying from that page saves you filling anything in. Everything below uses a placeholder instead.

Add the server

Antigravity reads MCP servers from a file called mcp_config.json. You can add Mangobeds globally, or for one workspace:

• Everywhere: ~/.gemini/config/mcp_config.json in your home folder.
• For one workspace: .agents/mcp_config.json in that workspace.

You can also reach the file from inside the editor: click … at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config.

Add this, replacing the placeholder with your own key, then reload Antigravity:

{
  "mcpServers": {
    "mangobeds": {
      "serverUrl": "https://api.mangobeds.com/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Then ask “what properties do I have in Mangobeds?” to check it works. It should answer without you giving it any IDs.

The one thing that catches everybody out: serverUrl

The key is serverUrl, not url. Google’s own documentation is blunt about it: legacy fields like url or httpUrl are not supported.

This matters because almost every other MCP guide on the internet, ours for Cursor and VS Code included, uses url. Paste one of those into Antigravity and the file is still valid JSON, so nothing complains: the server simply never connects. If Mangobeds is not showing up and you copied a config from somewhere else, check this first.

Keeping your key out of the file

A workspace file sits inside your project, so if that project is a repository, add .agents/mcp_config.json to .gitignore or your API key ends up committed. Antigravity also supports environment variable substitution, so you can write ${MANGOBEDS_API_KEY} as the header value and set that variable in your shell instead. Or use the home folder version and avoid the question.

What you can ask

Antigravity can list your properties itself, then answer from your live data: bookings and who is checking in, availability, why a room is blocked on a date, what a room costs on a given day, your seasonal rates, and your guests. It can also read these help guides, so “how do I set up seasonal rates?” is answered next to what your own rates actually say. With permission it can correct a guest’s details, add a guest to a booking, and send one of your saved messages.

An API key carries every permission, so a connection made this way can do all of it, including sending a real email or WhatsApp to a guest. If you would rather grant read-only access, Claude in the browser asks you to tick what it may do. Either way, anything it changes is written into the booking’s activity.

If it does not connect

• Check you used serverUrl, as above. This is the most common cause by a distance, and it fails silently.
• Check the JSON is valid. A stray comma or a duplicated mcpServers block stops the whole file loading, not just the new entry.
• Reload Antigravity. It reads the config at startup, so changes need a reload.
• Check the key. Copy it again from Apps > MCP. If the key was deleted and regenerated, the old one stops working immediately.
• Start a new conversation. Antigravity picks up the available tools when one begins, so an older thread may still be working from a previous set.