What the Bridge Does
The bridge acts as a protocol adapter:- Input: JSON-RPC messages over stdio from MCP clients
- Output: HTTP REST calls to HandsAI server at
http://localhost:8080 - Benefits: Zero configuration for clients, single integration point
Prerequisites
Go Installed (for building from source)
Installation
- Download Binary
- Build from Source
Download the pre-built binary from the releases page:
Replace
handsai-mcp-linux with handsai-mcp-macos or handsai-mcp-windows.exe based on your platform.Configuration for MCP Clients
Claude Desktop
Add HandsAI to your Claude Desktop configuration:Locate Configuration File
Find your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Antigravity (VS Code Extension)
Configure HandsAI in Antigravity’s MCP settings:Open MCP Configuration
In VS Code, find the Antigravity MCP configuration file:
- macOS/Linux:
~/.config/antigravity/mcp_config.json - Windows:
%APPDATA%\antigravity\mcp_config.json
Generic MCP Client
For any MCP-compatible client:Advanced Configuration
Custom HandsAI Server URL
If HandsAI is running on a different host or port, create aconfig.json file in the same directory as handsai-mcp:
config.json
Environment Variables
Alternatively, set the HandsAI URL via environment variable:Testing the Connection
Test Bridge Manually
Run the bridge in standalone mode:Send a test JSON-RPC message:You should receive a list of available tools.
Usage in Action
Claude Desktop Example
Claude executing a weather tool from HandsAI:
Claude sending an email via HandsAI + Resend:
Antigravity Example
Antigravity using HandsAI to check weather:
Troubleshooting
Bridge not connecting to HandsAI
Bridge not connecting to HandsAI
-
Verify HandsAI is running:
- Check the bridge logs for connection errors
- Ensure no firewall is blocking localhost:8080
MCP client doesn't see tools
MCP client doesn't see tools
- Verify the bridge binary path is absolute in the config
- Restart the MCP client completely
-
Check that tools are registered in HandsAI at
http://localhost:8080 - Test the bridge manually (see Testing section above)
Permission denied when running bridge
Permission denied when running bridge
Make the binary executable:
Tools not updating after adding new ones
Tools not updating after adding new ones
The bridge caches tool definitions. Restart your MCP client to refresh the tool list.
What’s Next?
Register APIs
Start registering external APIs as tools
Use Cases
Explore pre-built integrations and examples

