chnjinlei/hive

Fork 0

Files

T

Richard Tang 913d318ada docs: emphasize restarting Antigravity after MCP setup, fix config path and skill names

2026-02-11 15:57:11 -08:00

7.9 KiB

Raw Blame History

Antigravity IDE Setup

Use the Hive agent framework (MCP servers and skills) inside Antigravity IDE (Google’s AI IDE).

Quick start (3 steps)

Repo root = the folder that contains core/, tools/, and .antigravity/ (where you cloned the project).

Open a terminal and go to the hive repo root (e.g. cd ~/hive).
Run the setup script (use ./ so the script runs from this repo; don't use /scripts/...):
```
./scripts/setup-antigravity-mcp.sh
```
Restart Antigravity IDE. You should see agent-builder and tools as available MCP servers.

Important: Always restart/refresh Antigravity IDE after running the setup script or making any changes to MCP configuration. The IDE only loads MCP servers on startup.

Done. For details, prerequisites, and troubleshooting, read on.

What you get after setup

agent-builder – Create and manage agents (goals, nodes, edges).
tools – File operations, web search, and other agent tools.
Skills – Guided docs for building and testing agents (in .antigravity/skills/ or .claude/skills/).

Prerequisites

Antigravity IDE installed.
Python 3.11+ and project dependencies. If you haven’t set up the repo yet, from repo root run:
```
./scripts/setup-python.sh
```
MCP server dependencies (one-time). From repo root:
```
cd core && ./setup_mcp.sh
```

Full setup (step by step)

Step 1: Install MCP dependencies (one-time)

From the repo root:

cd core
./setup_mcp.sh

This installs the framework and MCP packages and checks that the server can start.

Step 2: Register MCP servers with Antigravity

Antigravity reads MCP config from your user config file (~/.gemini/antigravity/mcp_config.json), not from the project. The easiest way is to run the setup script from the hive repo folder:

./scripts/setup-antigravity-mcp.sh

The script finds the repo root, writes ~/.gemini/antigravity/mcp_config.json with the right paths, and you don't edit any paths by hand.

Important: Always restart/refresh Antigravity IDE after running the setup script. MCP servers are only loaded on IDE startup.

The agent-builder and tools servers should show up after restart.

Using Claude Code instead? Run:

./scripts/setup-antigravity-mcp.sh --claude

That writes ~/.claude/mcp.json as well.

Prefer to do it manually? See Manual MCP config below. You’ll create ~/.gemini/mcp.json (or ~/.claude/mcp.json) with absolute paths to your repo’s core and tools folders.

Step 3: Ignore the `cwd` warning (if you see it)

If the IDE says cwd is not allowed in the MCP config, you can ignore it. cwd is valid; the warning is from the schema and can be ignored.

Step 4: Use skills

Skills are guides (workflow, building, testing) in .antigravity/skills/ (they point to .claude/skills/). If Antigravity doesn’t show a “skills” UI, open those folders in the project and use the files as reference while you use the MCP tools.

Skill	What it's for
hive	End-to-end workflow for building and testing agents
hive-concepts	Core ideas for goal-driven agents
hive-create	Step-by-step agent construction
hive-patterns	Patterns and best practices
hive-test	Goal-based evaluation and testing
hive-credentials	Set up and manage agent credentials

What’s in the repo (`.antigravity/`)

.antigravity/
├── mcp_config.json   # Template for MCP servers (agent-builder, tools)
└── skills/           # Symlinks to .claude/skills/

The setup script writes your user config (~/.gemini/antigravity/mcp_config.json) using paths from this repo. The file in .antigravity/ is the template; Antigravity itself uses the file in your home directory.

Troubleshooting

MCP servers don’t connect

Run the setup script again from the hive repo root: ./scripts/setup-antigravity-mcp.sh, then restart Antigravity.
Make sure Python and deps are installed: from repo root run ./scripts/setup-python.sh.
Check that the servers can start: from repo root run
cd core && python3 -m framework.mcp.agent_builder_server (Ctrl+C to stop), and in another terminal
cd tools && PYTHONPATH=src python3 mcp_server.py --stdio (Ctrl+C to stop).
If those fail, fix the errors first (e.g. install deps).

“Module not found” or import errors

Open the repo root as the project in the IDE (the folder that has core/ and tools/).
If you edited ~/.gemini/mcp.json by hand, make sure cwd is the absolute path to core and tools (e.g. /Users/you/hive/core and /Users/you/hive/tools).

Skills don’t show up in the UI

Antigravity may not have a dedicated “skills” panel. Use the files in .claude/skills/ or .antigravity/skills/ as docs; the MCP tools (agent-builder, tools) still work.

Verification prompt (optional)

Paste this into Antigravity to check that MCP and skills are set up. It doesn’t use your machine’s paths; anyone can use it.

Check the Hive + Antigravity integration:

1. MCP: List available MCP servers/tools. Confirm that "agent-builder" and "tools" (or equivalent) are connected. If not, tell the user to run ./scripts/setup-antigravity-mcp.sh from the hive repo root, then restart Antigravity (see docs/antigravity-setup.md).

2. Skills: Confirm that the project has .antigravity/skills/ (or .claude/skills/) with: hive, hive-concepts, hive-create, hive-patterns, hive-test, hive-credentials.

3. Result: Reply with PASS (MCP + skills OK), PARTIAL (only skills or only MCP), or FAIL (neither), and one line on what to fix if not PASS.

If you get PARTIAL (e.g. MCP not connected), run ./scripts/setup-antigravity-mcp.sh from the repo root and restart Antigravity.

Manual MCP config template

Use this only if you don’t want to run the setup script. Replace /path/to/hive with your actual repo root (e.g. the output of pwd when you’re in the hive folder).

Save as ~/.gemini/antigravity/mcp_config.json (Antigravity) or ~/.claude/mcp.json (Claude Code), then restart the IDE to load the new configuration.

{
  "mcpServers": {
    "agent-builder": {
      "command": "python3",
      "args": ["-m", "framework.mcp.agent_builder_server"],
      "cwd": "/path/to/hive/core",
      "env": {
        "PYTHONPATH": "../tools/src"
      }
    },
    "tools": {
      "command": "python3",
      "args": ["mcp_server.py", "--stdio"],
      "cwd": "/path/to/hive/tools",
      "env": {
        "PYTHONPATH": "src"
      }
    }
  }
}

Use python instead of python3 if that’s what you have.

Verify from the command line (optional)

From the repo root:

Check that config and skills exist

test -f .antigravity/mcp_config.json && echo "OK: mcp_config.json" || echo "MISSING"
for s in hive hive-concepts hive-create hive-patterns hive-test hive-credentials; do
  test -L .antigravity/skills/$s && test -d .antigravity/skills/$s && echo "OK: $s" || echo "BROKEN: $s"
done

Check that the config is valid JSON

python3 -c "import json; json.load(open('.antigravity/mcp_config.json')); print('OK: valid JSON')"

Test that MCP servers start (two terminals)

# Terminal 1
cd core && PYTHONPATH=../tools/src python3 -m framework.mcp.agent_builder_server

# Terminal 2
cd tools && PYTHONPATH=src python3 mcp_server.py --stdio

If both start without errors, the config is fine.

7.9 KiB Raw Blame History Unescape Escape