Jan
Give models in Jan access to your memos.
Connect with the GigaRAG CLI
Jan 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 jan
Paste what it prints, then restart Jan afterwards. Nothing here expires, and gigarag connect --remove takes GigaRAG back out of everything it touched.
Sign in with GigaRAG
Connect without a key: Jan opens your browser, you sign in to GigaRAG and pick this workspace.
Jan only signs in when you have not set an Authorization header yourself.
- 1.
Add GigaRAG as below, without the header
Jan registers itself with GigaRAG and opens your browser.
- 2.
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 set it up by hand
- 1.
Open Settings, then MCP Servers, then Add MCP Server
Set the transport to HTTP and name it gigarag.
- 2.
Paste this as the URL
Server URLhttps://mcp.gigarag.com/mcp
- 3.
Add an Authorization header with this value
AuthorizationBearer <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 in Jan