Any MCP client
For any app that supports MCP servers, including ones not listed here.
Connect with the GigaRAG CLI
RecommendedAny MCP client keeps its settings somewhere a command cannot safely rewrite, so the CLI prints exactly what to enter instead. Signing in still happens in your browser, and no key is written into any config file.
npm install -g gigarag gigarag login gigarag connect any-mcp-client
Paste what it prints, then restart Any MCP client afterwards. Nothing here expires, and gigarag connect --remove takes GigaRAG back out of everything it touched.
Sign in with GigaRAG
Connect without a key: Any MCP client opens your browser, you sign in to GigaRAG and pick this workspace.
- 1.
Add a remote server with only the URL, and choose OAuth if asked
- 2.
Paste this as the server URL
Server URLhttps://mcp.gigarag.com/mcp
- 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.
Apps that support remote servers
- 1.
Add a remote server using Streamable HTTP
It may be called HTTP, Streamable HTTP or remote. If only SSE is offered, the app is too old to connect.
- 2.
Paste this as the server URL
Server URLhttps://mcp.gigarag.com/mcp
- 3.
Add an Authorization header with this value
AuthorizationBearer <api-key>
Needs an API key. Get one from API keys.
Apps that only run local servers
mcp-remote runs on your machine and passes requests to GigaRAG. It needs Node.js and is a community package.
- 1.
Add this to the app's MCP config
MCP config{ "mcpServers": { "gigarag": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.gigarag.com/mcp", "--header", "Authorization:${GIGARAG_AUTH}" ], "env": { "GIGARAG_AUTH": "Bearer <api-key>" } } } }Needs an API key. Get one from API keys.
Check it worked
Send this once it is connected. An answer drawn from your workspace means the connection is live.
List my GigaRAG buckets.