Manage Windows files
with local MCP.

Understand the connection

WhimRoom exposes a local standard-input/output MCP server to a compatible client. This is not a public remote connector endpoint, an official provider endorsement or proof of compatibility with every assistant.

The executable and arguments must match the installed build. Use the setup instructions and configuration example. The focused profiles are space, documents and folders; all exposes the full reference. Tool names retain the spacepilot prefix for compatibility.

Approve a small personal scope

Start with disposable test files in an ordinary personal folder. Check the client’s requested access and the app’s approved roots. Read a directory listing or storage observation first; inspect which paths and metadata return to the client.

Scope is not a blanket secrecy guarantee. Explicit inventory tools can report system registration metadata under their documented contracts. A document-reading tool can return text, and the assistant’s provider can receive the tool response.

Ask for a plan with evidence

Inspect only the test folder I approved. Identify the largest locally available files and show paths, sizes, skipped entries and evidence. Do not remove, move, download or organize anything. Explain which findings are observations and which still need my decision.

This is an example request, not an enforcement mechanism. The app and tool contracts enforce the actual boundary. Check every proposed source, destination and conflict rather than relying on the assistant’s summary.

For organization, request a supported plan such as spacepilot_plan_organization. For connected storage, inspect availability before a copy plan. The complete tool reference defines exact schemas and limitations.

Review supported changes in the app

Interactive file changes use a separate native review for supported plans. Model arguments are not your approval. If files or destinations change after planning, treat the plan as stale and obtain fresh evidence rather than bypassing validation.

Tool annotations describe expected behavior; they are not a substitute for authorization or a security boundary. Saved automation policies are a distinct choice and may not request fresh interactive approval for each run.

Check both output and exposure

After an approved test operation, inspect the actual destination and recorded outcome. Check skipped items and failures. Do not let a verified copy silently become a deletion instruction.

Review the MCP client’s conversation and retention controls as well as the app’s local records. Keep secrets out of prompts and sample paths. You can use the native workflows without enabling MCP; external AI accounts and fees are separate.

Continue with organization planning, copy verification and file-safety boundaries.