Config tools (MCP)
Generated content. This page is produced by
cargo run --bin gen_docs(src-tauri/src/bin/gen_docs/) reading the livermcp::ToolRouterthis crate's MCP server actually registers (McpServer::tool_router_*insrc-tauri/src/mcp/), viaToolRouter::list_all(), re-run on every docs-site build. Do not hand-edit it: fix the generator or the source it reads instead.
Each tool below is a thin wrapper over the identical operation the HTTP and gRPC APIs expose: same underlying MaslowService method, same effect on the machine, just a different transport. The See also line under each tool cross-references the other two surfaces, found by matching the tool's name against the real HTTP route table and the compiled proto descriptor (not a hand-maintained mapping, so it can't point at the wrong route).
get_config_entry
Get a single FluidNC config entry by its path. Read-only; requires a config dump to have run at least once (see list_config_entries).
See also: HTTP GET /v1/configEntries/*path · gRPC ConfigService.GetConfigEntry
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | yes | Full FluidNC config path, e.g. "axes/x/steps_per_mm". |
list_config_entries
List every known FluidNC config entry (path, value, kind). Read-only; pass force_refresh to request a fresh dump from the machine instead of serving the cached one.
See also: HTTP GET /v1/configEntries · gRPC ConfigService.ListConfigEntries
| Parameter | Type | Required | Description |
|---|---|---|---|
force_refresh | boolean | no | When true, request a fresh dump from the machine instead of serving the last cached one. |
update_config_entry
Write a FluidNC config entry's value, optionally persisting it to flash. This changes machine behavior (e.g. steps-per-mm, work area size); an incorrect value can cause unexpected motion on the next command.
See also: HTTP PATCH /v1/configEntries/*path · gRPC ConfigService.UpdateConfigEntry
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | yes | Full FluidNC config path, e.g. "axes/x/steps_per_mm". |
save | boolean | no | Whether to also persist the change to flash after writing it. |
value | string | yes | New value to write, as a string. |