Gemini CLI blueDEX Resource/blueDEX transparency

How to: Gemini CLI blueDEX blueDEX transparency

client:Gemini CLI transport:streamable-http resource:blueDEX transparency

Add blueDEX to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "bluedex": {
      "httpUrl": "https://dex.mk/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
blueDEX transparency 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 blueDEX 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 14 November 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.

blueDEX MCP server