Reflect the new onboarding wizard, multi-client one-click flow,
Claude Desktop transport auto-coercion, and startup config rewrite
in the README. Update the Claude Desktop section of the configurator
guide to drop the stale "throw on HTTP" language.

JsonFileMcpConfigurator.CheckStatus deserialized the standard
mcpServers layout through McpConfigServer.url, so HTTP configs
that use serverUrl (Antigravity 2.0, Windsurf) or httpUrl
(Gemini CLI) parsed with configuredUrl=null. The configurator
then reported transport=Unknown and status=IncorrectPath even
right after a successful Configure() that wrote a valid HTTP
entry, and the new startup auto-rewrite path kept rewriting
those files every Editor launch.

Switch the standard-layout branch to JObject parsing (same
shape as the VS Code branch) and accept url / serverUrl /
httpUrl. Add CheckStatus tests that lock all three property
names against a synthetic configurator.

…very (CoplayDev#1138)

The converter was declared public with a default constructor, so generic
Newtonsoft scanners (e.g. jillejr's newtonsoft-json-for-unity converters)
could pick it up and bind it into JsonConvert.DefaultSettings. Once
attached globally, any unrelated project code serializing a struct or
class containing a UnityEngine.Object reference would silently get an
asset path string back instead of the expected object JSON — purely from
having MCP for Unity installed.

Make the converter internal and expose Runtime internals to the Editor
and test assemblies via a Runtime AssemblyInfo so existing internal
consumers (UnityJsonSerializer, GameObjectSerializer) keep compiling.

…ction (CoplayDev#1134)

AssetImportWorker is a separate Editor subprocess that doesn't host the
MCP transport, so it has no reason to scan loaded assemblies. But our
[InitializeOnLoad] path runs there too, and Mono's reflection layer can
hard-crash inside type.GetCustomAttribute<T>() when assembly metadata
isn't fully restored after domain reload in the worker process — the
crash in the linked report freezes/kills the main Editor through the
import worker's IPC channel.

Detect the worker process via AssetDatabase.IsAssetImportWorkerProcess
(looked up reflectively so we tolerate visibility differences across
Unity versions) with a -importWorker command-line fallback, and bail
out of AutoDiscoverCommands before scanning. As a secondary belt, wrap
GetCustomAttribute<T>() in a try/catch helper so any single bad type
no longer aborts the entire registration pass.

CoplayDev#946)

FastMCP derives the wire schema from each tool's type annotations.
execute_custom_tool declared `parameters: dict | None`, which generates
a permissive schema some strict clients (Roo Code, certain VSCode MCP
adapters) reject during tool discovery — the tool then appears missing
even though everything else is healthy.

Switch to `dict[str, Any] | None` so the generated schema includes
proper additionalProperties bounds. The four other files cited in CoplayDev#946
(custom_tool_service, manage_components, manage_material, manage_texture)
were already parametrised in prior commits; execute_custom_tool was the
last remaining MCP-exposed tool with a bare `dict` annotation.

…ayDev#865)

Multi-agent and sub-agent workflows churn through stdio connections —
each new agent triggers a connect → close-stale → exit cycle, so the
three associated McpLog.Info calls in StdioBridgeHost flooded the Unity
console (the reporter saw 185+ lines in a single session). They're
useful for debugging a single hung connection but pure noise during
normal multi-agent operation.

Move all three to always:false so they only surface when verbose
logging is on, matching the existing recv-frame log on the same path.
Lifecycle messages that fire once (startup, port switch) and warnings
about anomalies (TCS timeout, queue eviction) are left at INFO.

Now that "Configure All Detected Clients" actually does what its name
says (auto-rewrite + per-client transport coercion + IsInstalled
filtering all landed in the recent client-config work), it's the path
we want first-run users on — not buried at the bottom of the panel.

Layout changes in McpClientConfigSection.uxml:
- Move the Configure-All button to the top of the section, right under
  the "Client Configuration" header, with a one-line helper underneath.
- Wrap the dropdown / status / single-client Configure button / Claude
  CLI path / project-dir / Manual Configuration foldout in a new
  "Configure a single client" foldout, collapsed by default. Persist
  its open/closed state via a new EditorPrefs key.

Style changes in Common.uss:
- New .primary-button class (bright green, 34px, bold) for the
  one-click action so it visually distinguishes itself from the regular
  blue .action-button rows.
- Light/dark-aware foldout header styling for the new client-details
  foldout that matches the existing manual-command-foldout treatment.

…t setup"

Helper line under the green button was visual noise — the button label
already says what it does. "Configure a single client" was redundant
inside a section titled "Client Configuration"; "Per-client setup"
reads cleaner. Also drop the now-orphan .primary-button-hint style.

…allowlist

The whole manage_vfx tool dispatcher and every VfxGraph* helper is
gated behind '#if UNITY_VFX_GRAPH', but nothing in the Editor asmdef
ever defined that symbol. Users with com.unity.visualeffectgraph
properly installed (e.g. Unity 6.3 + VFX Graph 17.x) hit the false
"VFX Graph package (com.unity.visualeffectgraph) not installed" branch
for every action, including read-only ones like list_templates and
get_info — reported via Discord.

Add a versionDefines entry to MCPForUnity.Editor.asmdef so Unity sets
UNITY_VFX_GRAPH whenever the VFX Graph package is present at any
version (`expression: 0.0.0`). This is the canonical way to detect
optional packages and lets the existing #if branches do their job.

Also drop ValidateVfxGraphVersion's hard-coded {"12.1"} allowlist,
which only matches Unity 2022.3-era VFX Graph and would still block
CreateAsset on modern installs even after the compile-gate fix. The
asset-level APIs we touch (VisualEffectAsset, AssetDatabase.CopyAsset,
template enumeration via PackageInfo) are stable across the
12.x → 17.x range, so the safer guard is just "package present" with
the compile-time gate handling the real "not installed" path.

…ailure

AddDependencyRow's click handlers flipped the button to "Installing..."
and only restored it inside a synchronous try/catch. But the per-package
call sites passed `() => InstallUpmPackage(...)` — no onComplete — so
when the UPM AddAndRemove request eventually completed (success OR
failure), nothing in PollUpmRequest's continuation ever told the button
to revert. A network timeout on com.unity.cinemachine therefore parked
the button on "Installing..." forever (Discord report); same for
Removing... on uninstall. The "Install All" path was fine because it
already threaded an onComplete callback through.

Change the install/uninstall hooks to Action<Action>, thread a `restore`
callback from the click handler into the UPM helpers, and invoke it
from PollUpmRequest's completion regardless of StatusCode. Roslyn (the
one synchronous install) just invokes the callback inline after Install
returns. The unrelated CRLF/LF noise in the diff is a side effect of
normalizing the file (988 CRLF lines, 41 LF lines pre-existing) onto
the dominant CRLF convention while my edits were in flight.

…custom_tool (PR review)

Two review nits from PR CoplayDev#1142.

McpClientConfiguratorBase.IsInstalled defaulted to `true`, which meant
any future configurator that derives directly from the base (without
going through JsonFile/Codex/ClaudeCli) would be treated as "detected"
by ConfigureAllDetectedClients and could end up writing config files
for apps that aren't on the machine. Default to a cheap filesystem
check via ParentDirectoryExists(GetConfigPath()); the three existing
base classes that override with the same check are harmlessly redundant
now, and CLI configurators (where GetConfigPath isn't a real path) keep
their own overrides.

execute_custom_tool declared `parameters: dict[str, Any] | None = None`
in its signature but then rejected `None` at runtime with
"parameters must be an object/dictionary". For parameter-less custom
tools the type hint and the behavior contradicted each other. Coerce
`None` to an empty dict; reject only genuinely-wrong types.

…ish (PR review)

Four smaller items flagged on PR CoplayDev#1142.

MCPSetupWindow.OnConfigureSelectedClicked marked setup as completed
and closed the window even when the user hadn't ticked any client —
clicking "Configure Selected" with everything unchecked would silently
skip setup forever. Show a prompt and return early instead.

README listed Claude Desktop under the HTTP-default group while a
neighboring paragraph correctly says Claude Desktop is stdio-only;
removed it from the HTTP list and pointed at the stdio block.

StartupConfigRewrite_TypeExists only checked that the type resolved,
not that it's public — added an explicit IsPublic assertion so the
test matches its own message about the [InitializeOnLoad] requirement.

ConfigureDetectedClientsTests calls the real ClientConfigurationService
which walks McpClientRegistry and Configure()s every detected client —
on CI this is harmless (no clients installed) but on a dev machine it
mutates real user config files. Marked both tests [Explicit] until we
DI the configurator list through the service.