docs: clarify MCP config fallback

[singhvishalkr]

Issue

Fixes #7868

Context

The MCP guide explains the settings UI flow, but it does not clearly say which config file to edit when adding a server through the UI is unavailable or fails.

Implementation

Add a short fallback note to the MCP setup section that points users to the project and global Kilo config files and the top-level mcp key.

Screenshots / Video

N/A, docs-only copy change.

How to Test

Manual/local verification

• Reviewed the updated MCP setup section for placement and Markdoc syntax.
• Ran git diff --check.

Reviewer test steps

1. Open the MCP guide.
2. Confirm the "Editing MCP Settings" section now explains which Kilo config file to edit if the UI cannot add a server.

Blocked checks and substitute verification

• bun run --filter @kilocode/kilo-docs build could not be run because Bun is not installed in this Windows session; substitute verification was the focused Markdown/Markdoc review and git diff --check.

Checklist

• Issue linked above, or exception explained
• Tests/verification described
• Screenshots/video included for visual changes, or marked N/A
• Changeset considered for user-facing changes
• I personally reviewed the diff and can explain the changes.

[vercel]

@singhvishalkr is attempting to deploy a commit to the Kilo Code Team on Vercel.

A member of the Team first needs to authorize it.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 files)

• packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md

Previous Review Summary (commit 5c9ac52)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 5c9ac52)

Status: 1 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

WARNING

File	Line	Issue
packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md	32	The new fallback note only points to .kilo/kilo.json[c], which can send users to create a second project config instead of editing an existing ./kilo.json[c].

Files Reviewed (1 files)

• packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md - 1 issue

---

_{Reviewed by gpt-5.4-20260305 · Input: 75.9K · Output: 4.6K · Cached: 146.4K}

_{Review guidance: REVIEW.md from base branch main}

[johnnyeric]

Thanks for the contribution! Merged