release: v0.3.1

docs/CONFIGURATION.md

@@ -15,6 +15,9 @@ Overrides:
 
 If both are set, `--config` wins. Environment variable overrides are applied after the file is loaded.
 
+To bootstrap MCP and skills directories at their resolved paths, run `deepseek setup`.
+To only scaffold MCP, run `deepseek mcp init`.
+
 ## Profiles
 
 You can define multiple profiles in the same file:
@@ -124,4 +127,9 @@ Use `deepseek features list` to inspect known flags and their effective state.
 
 ## Notes On `deepseek doctor`
 
-`deepseek doctor` checks default locations under `~/.deepseek/` (including `config.toml` and `mcp.json`). If you override paths via `--config` or `DEEPSEEK_MCP_CONFIG`, the doctor output may not reflect those overrides.
+`deepseek doctor` now follows the same config resolution rules as the rest of the CLI.
+That means `--config` / `DEEPSEEK_CONFIG_PATH` are respected, and MCP/skills checks
+use the resolved `mcp_config_path` / `skills_dir` (including env overrides).
+
+To bootstrap missing MCP/skills paths, run `deepseek setup --all`. You can also
+run `deepseek setup --skills --local` to create a workspace-local `./skills` dir.

docs/MCP.md

@@ -2,6 +2,16 @@
 
 DeepSeek CLI can load additional tools via MCP (Model Context Protocol). MCP servers are local processes that the CLI starts and communicates with over stdio.
 
+## Bootstrap MCP Config
+
+Create a starter MCP config at your resolved MCP path:
+
+```bash
+deepseek mcp init
+```
+
+`deepseek setup --mcp` performs the same MCP bootstrap alongside skills setup.
+
 ## Config File Location
 
 Default path:
@@ -13,6 +23,8 @@ Overrides:
 - Config: `mcp_config_path = "/path/to/mcp.json"`
 - Env: `DEEPSEEK_MCP_CONFIG=/path/to/mcp.json`
 
+`deepseek mcp init` (and `deepseek setup --mcp`) writes to this resolved path.
+
 After editing the file, restart the TUI.
 
 ## Tool Naming
@@ -61,7 +73,6 @@ MCP tools currently execute without TUI approval prompts. Only configure MCP ser
 
 ## Troubleshooting
 
-- Run `deepseek doctor` to confirm whether the default `~/.deepseek/mcp.json` exists.
-- If you override `mcp_config_path` / `DEEPSEEK_MCP_CONFIG`, note that `deepseek doctor` still checks `~/.deepseek/mcp.json`.
+- Run `deepseek doctor` to confirm the MCP config path it resolved and whether it exists.
+- If the MCP config is missing, run `deepseek mcp init --force` to regenerate it.
 - If tools don’t appear, verify the server command works from your shell and that the server supports MCP `tools/list`.
-