Kimi Code CLI
Moonshot's terminal coding agent, the successor to Kimi CLI.
Connect with the GigaRAG CLI
One command connects Kimi Code CLI 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 Kimi Code CLI afterwards. Nothing here expires, and gigarag connect --remove takes GigaRAG back out of everything it touched.
Sign in with GigaRAG
Connect without a key: Kimi Code CLI opens your browser, you sign in to GigaRAG and pick this workspace.
- 1.
Add GigaRAG without a key
~/.kimi-code/mcp.json{ "mcpServers": { "gigarag": { "url": "https://mcp.gigarag.com/mcp" } } } - 2.
Start the sign-in from a Kimi Code session
/mcp-config 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 Kimi Code CLI. It carries your agent key and tells the agent exactly what to change, so it sets the connection up itself.
Merge into ~/.kimi-code/mcp.json under mcpServers.gigarag:
{ "url": "https://mcp.gigarag.com/mcp", "headers": { "Authorization": "Bearer <api-key>" } }
Tell me to restart Kimi Code. Don't repeat the key.Or set it up by hand
- 1.
Add GigaRAG to your MCP config
Merge it into mcpServers if the file already has other servers.
~/.kimi-code/mcp.json{ "mcpServers": { "gigarag": { "url": "https://mcp.gigarag.com/mcp", "headers": { "Authorization": "Bearer <api-key>" } } } } - 2.
Restart Kimi Code
Run /mcp-config to see gigarag listed.
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: Kimi Code MCP