Connect AlmRecorder to Google Antigravity

Before you begin: confirm that AlmRecorder has Settings → MCP. If it is missing, install a version with MCP support.

Configure AlmRecorder as a local MCP server for Google Antigravity on this Mac.

Work carefully and perform the setup for me if you have filesystem and terminal access. If you cannot edit local files, return the exact ready-to-paste file change and tell me where it belongs.

1. First confirm that AlmRecorder shows Settings → MCP, is in its final app location, and is open.
2. Ask me to enable Enable local MCP server, wait for Listening on …, and choose Copy configuration.
3. I will append the copied JSON configuration below this task. Ask me for it if it is missing.
4. Treat ALMRECORDER_MCP_TOKEN like a password. Never repeat it in your response, log it, or put it in Git, a support issue, or a shared project file.
5. Merge the almrecorder entry under mcpServers in ~/.gemini/config/mcp_config.json. Use command, an empty args array, and both env values. A project-specific setup can instead live in .agents/mcp_config.json.
6. Use the exact command, ALMRECORDER_MCP_SOCKET, and ALMRECORDER_MCP_TOKEN copied from AlmRecorder. The transport is local stdio and AlmRecorderMCPBridge takes no arguments.
7. Do not alter or delete any other client settings. Show a diff or describe exactly what changed.
8. Open /mcp in Antigravity CLI or refresh MCP Servers in the IDE and confirm that almrecorder is connected.
9. Ask the agent to call get_library_status and report the recording count. Then call list_recordings with limit: 1. Do not change anything.
10. Do not enable AlmRecorder’s content or write permissions. I will choose those myself after the read-only check succeeds.

ALMRECORDER COPIED CONFIGURATION:
[Paste Copy configuration from AlmRecorder here]

Install the local client

Download Google Antigravity for macOS from antigravity.google/download. The current Mac build requires Apple Silicon.

If you prefer the terminal client, Google’s documented installer is:

curl -fsSL https://antigravity.google/cli/install.sh | bash

It installs the agy binary under ~/.local/bin by default. Start it once and complete Google sign-in.

AlmRecorder cannot connect to an Antigravity session running only in a remote or cloud environment. The IDE or CLI process that launches AlmRecorderMCPBridge must run on the same Mac as AlmRecorder.

Prepare AlmRecorder

1. Keep AlmRecorder.app in Applications and leave it open.
2. Turn off Allow MCP clients to access this recording on anything sensitive. Use Hide from MCP for private tags.
3. In Settings → MCP, leave the content and changes permissions off.
4. Turn on Enable local MCP server, wait for Listening on …, then choose Copy configuration.

Get the connection values

The token is copied—not revealed

AlmRecorder intentionally masks the real token in the on-screen preview. There is no visible token field to hunt for.

1. Open Settings → MCP in AlmRecorder.
2. Turn on Enable local MCP server and wait until Status says Listening on ….
3. Choose Copy configuration. The clipboard now contains the command, socket, and real ALMRECORDER_MCP_TOKEN.

Paste the configuration directly where this guide tells you. Treat it like a password and clear the clipboard after the connection works.

1 Choose Copy configuration

Permission boundary: Antigravity receives only what AlmRecorder permits. Metadata works first; transcripts, summaries, notes, comments, and changes remain blocked until you enable the corresponding switches.

Add it to Antigravity

In Antigravity IDE, open the agent side panel, choose … → MCP Servers → Manage MCP Servers → View raw config.

For a global installation, edit:

~/.gemini/config/mcp_config.json

For one trusted project only, use .agents/mcp_config.json in that workspace. Do not put the token in a project file that will be committed.

Merge the almrecorder entry under mcpServers:

{
  "mcpServers": {
    "almrecorder": {
      "command": "/Applications/AlmRecorder.app/Contents/MacOS/AlmRecorderMCPBridge",
      "args": [],
      "env": {
        "ALMRECORDER_MCP_SOCKET": "/Users/you/Library/Application Support/AlmRecorder/MCP/mcp.sock",
        "ALMRECORDER_MCP_TOKEN": "paste the token copied from AlmRecorder"
      }
    }
  }
}

Use the exact command, socket, and token from AlmRecorder. Preserve every existing server. The token is a secret stored in plain text, so the global private file is the safer default.

Refresh the server list in the IDE. In Antigravity CLI, enter /mcp to open the MCP Manager, reload configuration, and inspect the almrecorder connection.

Check the connection

Ask Antigravity:

Use AlmRecorder’s get_library_status tool and report the recording count. Then call list_recordings with limit: 1. Do not change anything.

A successful status response confirms that Antigravity launched the local bridge and connected to the open AlmRecorder app.

If it fails

• Server is missing: confirm the global path is ~/.gemini/config/mcp_config.json, or that the project file is exactly .agents/mcp_config.json.
• Bridge not found: AlmRecorder moved after you copied its absolute command. Copy the configuration again.
• Tools appear but calls fail: keep AlmRecorder open, enable its server, and refresh the socket/token values.
• Remote session: switch to a local Antigravity IDE or CLI session on the Mac running AlmRecorder.
• Configuration ignored: open /mcp or the IDE’s MCP manager and explicitly reload it.

Remove the almrecorder entry and reload MCP to disconnect Antigravity. Disable the server or rotate the token in AlmRecorder to revoke every configured client.

Google Antigravity MCP documentation · Antigravity installation · Privacy in AlmRecorder