Gemini CLI KnownFix Resource/Deno Deploy returns 508 Loop Detected when a deployment fetches its own…
How to: Gemini CLI KnownFix Deno Deploy returns 508 Loop Detected when a deployment fetches its own…
Add KnownFix to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"knownfix": {
"httpUrl": "https://knownfix-backend-28.b-hash88.deno.net/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Deno Deploy returns 508 Loop Detected when a deployment fetches its own… is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
-
04
If it does not appear, check that KnownFix is connected and that you are looking at its resources rather than its tools.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Same resource, other clients
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.