Set up your bridge.

1. On the receiver computer, open workspace .agents/mcp_config.json, or global ~/.gemini/config/mcp_config.json for all workspaces. Choose one scope.
2. Merge this mcpServers entry, replacing both absolute paths:

   {
     "mcpServers": {
       "health-bridge": {
         "command":
           "/ABS/PATH/health-bridge",
         "args": [
           "mcp", "start", "--db",
           "/ABS/PATH/health.sqlite3"
         ]
       }
     }
   }

3. Restart the CLI session, review any server/tool trust request, and check that health-bridge tools are available. Then try the first question.

Antigravity MCP documentation

1. On the receiver computer, open .mcp.json in your project root. This recipe uses project scope, not Claude Desktop settings.
2. Merge this mcpServers entry, replacing both absolute paths. Keep this private configuration out of shared source control:

   {
     "mcpServers": {
       "health-bridge": {
         "type": "stdio",
         "command":
           "/ABS/PATH/health-bridge",
         "args": [
           "mcp", "start", "--db",
           "/ABS/PATH/health.sqlite3"
         ]
       }
     }
   }

3. Restart Claude Code in that project, approve the project MCP server when asked, and inspect /mcp. Once connected, try the first question.

Claude Code MCP documentation

1. On the receiver Mac, open Claude Desktop → Settings → Developer → Edit Config: ~/Library/Application Support/Claude/claude_desktop_config.json. This is the desktop app, not Claude web/mobile; native Windows receiver setup is outside this recipe.
2. Merge this mcpServers entry, replacing both absolute paths:

   {
     "mcpServers": {
       "health-bridge": {
         "command":
           "/ABS/PATH/health-bridge",
         "args": [
           "mcp", "start", "--db",
           "/ABS/PATH/health.sqlite3"
         ]
       }
     }
   }

3. Completely quit and restart Claude Desktop. Review tool permissions and the server's connection status before trying the first question.

Full Claude Desktop walkthrough and troubleshooting · Official local-server tutorial

1. On the receiver computer, open ~/.codex/config.toml for your Codex CLI user configuration.
2. Add this table only if mcp_servers.health-bridge does not already exist; otherwise review that entry. Replace both absolute paths:

   [mcp_servers.health-bridge]
   command = "/ABS/PATH/health-bridge"
   args = [
     "mcp", "start", "--db",
     "/ABS/PATH/health.sqlite3"
   ]

3. Restart Codex CLI, review its MCP/tool approval settings, and inspect /mcp for health-bridge. Then try the first question.

Codex MCP documentation

1. On the receiver computer, open project .cursor/mcp.json, or global ~/.cursor/mcp.json for all projects. Choose one scope.
2. Merge this mcpServers entry, replacing both absolute paths:

   {
     "mcpServers": {
       "health-bridge": {
         "type": "stdio",
         "command":
           "/ABS/PATH/health-bridge",
         "args": [
           "mcp", "start", "--db",
           "/ABS/PATH/health.sqlite3"
         ]
       }
     }
   }

3. Restart Cursor and review the server in Cursor Settings → Tools & MCP. Enable it and review tool approvals before the first question. This is local editor setup, not cloud-agent access.

Cursor MCP documentation

1. On the receiver computer, open ~/.hermes/config.yaml for the default Hermes profile. If you use another profile, edit its own config.yaml instead.
2. Merge this server under the existing mcp_servers mapping. Preserve YAML indentation and replace both absolute paths:

   mcp_servers:
     health-bridge:
       command:
         "/ABS/PATH/health-bridge"
       args:
         - "mcp"
         - "start"
         - "--db"
         - "/ABS/PATH/health.sqlite3"

3. Restart Hermes with the same profile so it discovers the tools. Review access and run hermes mcp test health-bridge before the first question.

Full Hermes walkthrough and troubleshooting · Hermes MCP documentation

1. On the receiver computer, open ~/.openclaw/openclaw.json, or the explicit configuration file your gateway uses. This recipe targets OpenClaw-managed MCP, not every ACP harness.
2. Manually merge the health-bridge entry into mcp.servers. This is a strict JSON subset example, not an arbitrary JSON5 rewrite: retain unrelated settings, comments and syntax in your original file. Replace both absolute paths:

   {
     "mcp": {
       "servers": {
         "health-bridge": {
           "command":
             "/ABS/PATH/health-bridge",
           "args": [
             "mcp", "start", "--db",
             "/ABS/PATH/health.sqlite3"
           ]
         }
       }
     }
   }

3. Restart the gateway with that configuration, review tool permissions, and use openclaw mcp doctor health-bridge --probe to check the saved server. A config listing alone is not a connection test. Then try the first question.

OpenClaw configuration reference · Connection and probe documentation

1. On the receiver computer, open project opencode.json, or user ~/.config/opencode/opencode.json. Choose one scope.
2. Merge this mcp entry, replacing both absolute paths. OpenCode uses a single command array, not separate command and args fields:

   {
     "mcp": {
       "health-bridge": {
         "type": "local",
         "command": [
           "/ABS/PATH/health-bridge",
           "mcp", "start", "--db",
           "/ABS/PATH/health.sqlite3"
         ],
         "enabled": true
       }
     }
   }

3. Restart OpenCode in the intended project, review tool permissions, and inspect opencode mcp list. Then try the first question, asking it to use health-bridge.

OpenCode MCP documentation

1. On the receiver computer, open workspace .vscode/mcp.json in local desktop VS Code. For user scope, run MCP: Open User Configuration from the Command Palette and choose Local if asked for a destination. Do not select an SSH, container or remote host.
2. Merge this VS Code Local servers format entry, replacing both absolute paths. The servers wrapper is not the portable Copilot mcpServers format; this recipe does not configure all Copilot harnesses:

   {
     "servers": {
       "health-bridge": {
         "type": "stdio",
         "command":
           "/ABS/PATH/health-bridge",
         "args": [
           "mcp", "start", "--db",
           "/ABS/PATH/health.sqlite3"
         ]
       }
     }
   }

3. Use the config editor's Start action, or MCP: List Servers to restart health-bridge. Review the server trust dialog and tool permissions, then try the first question.

VS Code MCP setup · Local configuration reference