Gemini CLI RackArchitect MCP Resource/Current Declarative rack.yaml Source
How to: Gemini CLI RackArchitect MCP Current Declarative rack.yaml Source
Add RackArchitect MCP to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"rack-architect-mcp": {
"httpUrl": "https://mcp.rackarchitect.dev/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Current Declarative rack.yaml Source 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 RackArchitect MCP 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.