Disable .NET host's filesystem watcher (`mcp run`, `forwarder run`, possibly other entrypoints)

[nblumhardt]

Wanted to post this here in case anyone else runs into it. I was running into issues with the mcp not starting up in claude. Turns out, there is something about how seqcli mcp run uses its working directory at startup: it makes the CWD the .NET host's content root and recursively sets up file watching over it.

My repo is bind-mounted into a devcontainer from a Windows host (WSL2, so 9p). From the repo root it registers thousands of inotify watches over that mount, taking 20s+ (past 30s when cold). Claude Code's default MCP timeout is 30s, so it kept giving up. It's not hung, just slow: run the same command by hand and it answers initialize fine once it gets going. From an empty directory it's instant.

Two fixes:

• "timeout": 300000 on the server config, so Claude waits it out
• DOTNET_contentRoot= — drops the watch count to essentially zero, since this is an empty directory and starts immediately

Seq itself was fine (I think). Just wanted to provide a heads up

Originally posted by @userAXC001 in #459

[nblumhardt]

Thanks for the heads-up, @userAXC001, we'll take a look at this.