Menu
v0.10.1

Guides / Settings and where files go

Settings and where files go

The settings OODS Foundry reads, and the folders your work lives in.

Generated from @oods/foundry 0.10.1

The guide below is the one the package ships, README.md: Settings, Where things go in @oods/foundry@0.10.1, shown as written.

Settings

Environment variables are optional; every default is the documented one. Set them in the client's env block (Claude Desktop, Cursor) or with -e KEY=value after the name on claude mcp add.

VariableDefaultEffect
MCP_TOOLSETdefaultdefault advertises 20 tools; all adds the on-demand tool, 21 in all.
MCP_EXTRA_TOOLS(none)Comma-separated on-demand tools added to the default surface, for example a11y_scan.
MCP_ROLEdesignerPolicy role (designer or maintainer).
MCP_SCHEMA_STORE_ROOT~/.oods-foundryWhere saved schemas, every composed and previewed version, and file-mode output are kept.
OODS_NODE_PATHthe Node running the adapterNode binary used to start the native server.
OODS_MCP_APPS_UI(unset)1 offers the preview app on design_preview even to a client that did not negotiate the MCP Apps extension.
OODS_FOUNDRY_HOME~/.oods-foundryWhere import and intake drafts are staged and, when started with npx, where the runtime and every default folder below are kept. The Docker image sets it to /data.
OODS_OBJECTS_DIR~/.oods-foundry/objectsFolder your own objects are read from, after the ones OODS Foundry ships; the object_registry tool's register writes there.
OODS_TRAITS_DIR~/.oods-foundry/traitsFolder your own traits are read from, after the ones OODS Foundry ships.
OODS_BRANDS_DIR~/.oods-foundry/brandsFolder your own brands are kept in and built in, outside the runtime; brand_create's create writes there.
OODS_MAPPINGS_DIR~/.oods-foundry/mappingsFolder your component mappings are kept in (component-mappings.json), outside the runtime; component_map writes there.
MCP_MAPPINGS_PATH(unset)A mappings file used instead of that folder's; it takes precedence. A relative path resolves against the runtime directory.

Where things go

  • ~/.oods-foundry/runtime/<version>-<digest>/ holds the unpacked runtime, one directory per version. Delete an old one to reclaim its space; the current one is unpacked again if it is missing.
  • ~/.oods-foundry/schemas/, compositions/ and payloads/ hold your saved schemas, every composed and previewed version, and file-mode output. They survive upgrades; delete them to start over.
  • ~/.oods-foundry/objects/ and traits/ hold your own objects and traits. They survive upgrades.
  • ~/.oods-foundry/brands/ holds your own brands, and brands/.build/ the token build made from them. They survive upgrades.
  • ~/.oods-foundry/mappings/component-mappings.json holds your component mappings. It survives upgrades. OODS_MAPPINGS_DIR moves the folder; MCP_MAPPINGS_PATH names a mappings file instead, and takes precedence.
  • Run records from apply: true calls are written inside the unpacked runtime, under artifacts/current-state/<date>/, and go when you delete that version.

To remove OODS Foundry, remove the client entry and delete ~/.oods-foundry.