fix(mcp): use explicit mode for setupMCP during init

[binoy14]

Summary

• Adds explicit mode: 'prompt' | 'auto' | 'skip' option to setupMCP, replacing the previous skip boolean and internal isInteractive({skipCi: true}) check
• The caller (init command) now determines the mode based on flags and environment, instead of setupMCP guessing
• Removes skipCi parameter from isInteractive() (it was only used by setupMCP and produced incorrect behavior)

Before (broken):

Scenario	Behavior
CI (no TTY)	Auto-configured all editors
CI (with TTY)	Prompted user
--yes (user terminal)	Prompted user
Interactive	Prompted user

After (correct):

Scenario	Behavior
CI (any TTY)	Skips MCP entirely
--yes (user terminal)	Auto-configures all detected editors
Interactive	Prompts user

Files changed

• setupMCP.ts — replace skip with mode, remove isInteractive dependency
• init.ts — compute mcpMode from --no-mcp, CI detection, and --yes flag
• isInteractive.ts — remove skipCi param, simplify to no-arg function
• configure.test.ts — remove isInteractive mock and non-interactive test
• New setupMCP.test.ts — unit tests for all three mode behaviors

🤖 Generated with Claude Code

[claude]

Claude finished @binoy14's task in 2m 47s —— View job

---

Review

• Read changed files
• Analyze for bugs, logic errors, and issues
• Post review feedback

---

configure.ts:43 — Behavior change for CI+TTY

mode: isInteractive() ? 'prompt' : 'auto'

The old setupMCP internals used isInteractive({skipCi: true}), which meant CI+TTY → prompt. The new code uses isInteractive() (no skipCi), which returns false in any CI environment regardless of TTY, so CI+TTY now → auto-configure all editors without prompting.

This is a breaking behavior change for users running sanity mcp:configure interactively in a CI environment (e.g., an interactive terminal in a CI job). Consider whether 'auto' is the right fallback or if the original skipCi-like logic should be preserved for the explicit mcp configure command.

Fix this →

---

init.ts:468 — Silent MCP skip on --yes without TTY

if (!this.flags.mcp || !this.resolveIsInteractive()) {
  mcpMode = 'skip'
} else if (this.flags.yes) {
  mcpMode = 'auto'
}

If a user runs sanity init --yes without a TTY (e.g., piped input, no CI env var), resolveIsInteractive() returns false, MCP is silently skipped, and the --yes auto-configure path is never reached. No warning or debug message is emitted in this case. If --yes is meant to drive unattended installs without a TTY, MCP would unexpectedly not be configured. Consider adding a mcpDebug log when skipping due to non-interactive (non---no-mcp) conditions.

[github-actions]

Coverage Delta

File	Statements
packages/@sanity/cli-core/src/util/isInteractive.ts	100.0% (±0%)
packages/@sanity/cli/src/actions/mcp/setupMCP.ts	100.0% (+ 3.5%)
packages/@sanity/cli/src/commands/init.ts	92.6% (- 0.1%)
packages/@sanity/cli/src/commands/mcp/configure.ts	90.0% (±0%)

Comparing 4 changed files against main @ ff9f15f3f7a599b3bb06dbd25117e2d865623123

Overall Coverage

Metric	Coverage
Statements	82.0% (+ 0.0%)
Branches	71.0% (+ 0.1%)
Functions	80.2% (±0%)
Lines	82.4% (+ 0.0%)