Document how to use FineCode MCP with Copilot in VSCode

Author: Aksem

docs/cli.md

@@ -222,7 +222,9 @@ Start the FineCode MCP server on stdio. Connects to a running FineCode WM Server
 | `--workdir=<path>` | Workspace root directory (default: current directory). |
 | `--log-level=<level>` | Set log level: `TRACE`, `DEBUG`, `INFO`, `WARNING`, `ERROR` (default: `INFO`) |
 
-Typically started automatically by MCP-compatible clients (for example, Claude Code) — see [IDE and MCP Setup](getting-started-ide-mcp.md#mcp-setup-for-ai-clients).
+Typically started automatically by MCP-compatible clients (for example, Claude Code) or by VS Code Copilot when the FineCode VSCode extension registers the MCP provider.
+
+For setup details, see [IDE and MCP Setup](getting-started-ide-mcp.md#mcp-setup-for-ai-clients). If you use VS Code without the FineCode extension, use the fallback `.vscode/mcp.json` configuration from that page.
 
 ---
 

docs/getting-started-ide-mcp.md

@@ -37,6 +37,8 @@ To use the Testing panel, you need handlers registered for both actions. The `fi
 
 FineCode exposes an MCP server so any MCP-compatible client can invoke FineCode actions directly.
 
+If you use VS Code and the FineCode VSCode extension, prefer the extension-based integration for Copilot (recommended below). Manual MCP configuration is a fallback for setups without the extension.
+
 At a minimum, your client should launch:
 
 ```bash
@@ -63,5 +65,31 @@ Create `.mcp.json` in the workspace root:
 
 Claude Code discovers this file and prompts for approval on first use.
 
+### Example: VS Code Copilot (recommended with FineCode VSCode extension)
+
+When the FineCode VSCode extension is installed, it registers FineCode MCP servers for Copilot automatically.
+
+No manual MCP configuration is required.
+
+### Example: VS Code Copilot fallback (only without FineCode VSCode extension)
+
+Use this only if you are not using the FineCode VSCode extension.
+
+Create `.vscode/mcp.json` in the workspace root:
+
+```json
+{
+  "servers": {
+    "finecode": {
+      "type": "stdio",
+      "command": ".venvs/dev_workspace/bin/python",
+      "args": ["-m", "finecode", "start-mcp", "--workdir=${workspaceFolder}"]
+    }
+  }
+}
+```
+
+Note: VS Code uses the top-level `servers` key in `mcp.json`.
+
 Manual server startup is mainly for debugging and custom integration development.
 See [LSP and MCP Architecture](reference/lsp-mcp-architecture.md#manual-server-startup-for-debugging).

docs/index.md

@@ -21,7 +21,7 @@ FineCode lets you define actions once and run them through the surfaces develope
 
 - Local CLI: `python -m finecode run lint`
 - CI: run the same actions instead of re-creating tool wiring in pipelines
-- IDE: connect through the [VSCode and MCP setup guide](getting-started-ide-mcp.md)
+- IDE and AI: use the [VSCode and MCP setup guide](getting-started-ide-mcp.md) (extension path recommended, MCP fallback available)
 - AI assistants: expose the same action surface through MCP-compatible clients
 
 That means less duplicated glue code and fewer mismatches between "what works on my machine" and "what CI expects".
@@ -116,7 +116,7 @@ FineCode is not just a wrapper around linters and formatters. It gives those too
 ## Where to go next
 
 - [Getting Started](getting-started.md) for the full setup path
-- [IDE and MCP Setup](getting-started-ide-mcp.md) to connect editors and AI clients
+- [IDE and MCP Setup](getting-started-ide-mcp.md) for the recommended VSCode extension path and MCP fallback options
 - [Concepts](concepts.md) for the core mental model
 - [Why FineCode's Action Model Works](theory/why-action-model.md) for the design rationale
 - [Designing Actions](guides/designing-actions.md) for action design guidance