on main help sign in
docs(README): add note about shell expansion in MCP config
d745ff5Christian Rocha
README.md+11−4
@@ -292,10 +292,17 @@ like you would. LSPs can be added manually like so:
292
292
293### MCPs
293### MCPs
294
294
295−Crush also supports Model Context Protocol (MCP) servers through three
295+Crush also supports Model Context Protocol (MCP) servers through three transport
296−transport types: `stdio` for command-line servers, `http` for HTTP endpoints,
296+types: `stdio` for command-line servers, `http` for HTTP endpoints, and `sse`
297−and `sse` for Server-Sent Events. Environment variable expansion is supported
297+for Server-Sent Events.
298−using `$(echo $VAR)` syntax.
298+
299+Shell-style value expansion (`$VAR`, `${VAR:-default}`, `$(command)`, quoting,
300+and nesting (works in `command`, `args`, `env`, `headers`, and `url`, so
301+file-based secrets like work out of the box, so you can use values like
302+"$TOKEN"` and `"$(cat /path/to/secret/token)"``. Expansion runs through Crush's
303+embedded shell, so the same syntax works on all supported systems, including
304+Windows. Unset variables are an error; use `${VAR:-fallback}` to opt in to
305+a default.
299
306
300```json
307```json
301{
308{