OpenClaw
The self-hosted personal assistant that works across your chat apps.
Connect with the GigaRAG CLI
One command connects OpenClaw and every other AI tool on this machine. Signing in happens in your browser, so no key is written into any config file.
npm install -g gigarag gigarag login gigarag connect
Restart OpenClaw afterwards. Nothing here expires, and gigarag connect --remove takes GigaRAG back out of everything it touched.
Sign in with GigaRAG
Connect without a key: OpenClaw opens your browser, you sign in to GigaRAG and pick this workspace.
OpenClaw ignores an Authorization header while sign-in is on for a server.
- 1.
Add GigaRAG with sign-in
openclaw mcp set gigarag '{"url":"https://mcp.gigarag.com/mcp","transport":"streamable-http","auth":"oauth"}' - 2.
Start the sign-in
If your browser cannot reach OpenClaw, run the same command again with --code and the code the browser shows.
openclaw mcp login gigarag
- 3.
Sign in with your GigaRAG account
Your browser opens GigaRAG. Pick the workspace to share and approve. No key is stored in the app, and the connection does not expire.
Or paste a prompt
Paste this into OpenClaw. It carries your agent key and tells the agent exactly what to change, so it sets the connection up itself.
Run this to add GigaRAG: openclaw mcp add gigarag --url https://mcp.gigarag.com/mcp --transport streamable-http --header 'Authorization: Bearer <api-key>' Remove any existing gigarag first. Then run openclaw mcp probe gigarag and report back. Don't repeat the key.
Or set it up by hand
Some OpenClaw releases did not send custom headers over Streamable HTTP. If GigaRAG answers unauthorized, update OpenClaw.
- 1.
Run this where OpenClaw is installed
openclaw mcp add gigarag --url https://mcp.gigarag.com/mcp --transport streamable-http --header 'Authorization: Bearer <api-key>'
- 2.
Check the connection
openclaw mcp probe gigarag
- 3.
Or add it in the Control UI
Open Settings, then MCP, then Add server, choose Streamable HTTP, and use the same URL and header. The chat composer has the same form under +, then Connectors.
Or edit the config file
- 1.
Add GigaRAG under mcp.servers
~/.openclaw/openclaw.json{ "mcp": { "servers": { "gigarag": { "url": "https://mcp.gigarag.com/mcp", "transport": "streamable-http", "headers": { "Authorization": "Bearer <api-key>" } } } } }
Check it worked
Send this once it is connected. An answer drawn from your workspace means the connection is live.
List my GigaRAG buckets.
Written from the official docs: MCP servers, MCP registry commands, Configuration