Amazon Q Developer
Use your memos from Amazon Q Developer chat in your IDE.
Connect with the GigaRAG CLI
Amazon Q Developer 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 amazon-q
Paste what it prints, then restart Amazon Q Developer afterwards. Nothing here expires, and gigarag connect --remove takes GigaRAG back out of everything it touched.
Sign in with GigaRAG
Connect without a key: Amazon Q Developer opens your browser, you sign in to GigaRAG and pick this workspace.
- 1.
Add GigaRAG as below, but leave Headers empty
Amazon Q opens your browser to sign in when it connects.
- 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 the Q panel, then Chat, then the tools icon, then +
Choose global scope, name it gigarag and set transport to http.
- 2.
Paste this as the URL
Server URLhttps://mcp.gigarag.com/mcp
- 3.
Under Headers, add Authorization with this value
AuthorizationBearer <api-key>
- 4.
Click Save
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 in the IDE