Merge branch 'feat/mcp-client-playwright'

docs/telegram-bot.md

@@ -36,6 +36,9 @@ Environment variables, or the `Telegram` section of `appsettings.json` (`Telegra
 | `PROCESS_ENV_ALLOW` | — | Comma-separated names or globs let through to `bash`, scheduled scripts and MCP servers despite the deny-list (e.g. `GH_TOKEN` for `gh`). Added to `ProcessEnvironment:Allow` |
 | `ProcessEnvironment:Deny` / `ProcessEnvironment:Allow` | built-in deny-list | Added to the defaults (`*_API_KEY`, `*_TOKEN`, `*_SECRET`, `*_PASSWORD`, their `Section__Key` forms and the named provider credentials), never replacing them. Allowing a name that is denied by name stops startup |
 | `ProcessEnvironment:HardenHostProcess` | `true` | Linux: the bot process is made non-dumpable. `ProcessEnvironment__HardenHostProcess=false` for a debugging session only |
+| `PLAYWRIGHT_ENABLED` / `Mcp:Playwright:Enabled` | `false` | Browser tools through `@playwright/mcp` ([mcp.md](mcp.md)) |
+| `PLAYWRIGHT_HEADLESS`, `PLAYWRIGHT_BROWSER`, `PLAYWRIGHT_EXTRA_ARGS`, `PLAYWRIGHT_COMMAND` | `true`, `chromium`, —, `npx` | See [mcp.md](mcp.md#the-playwright-preset) |
+| `Mcp:Servers:<name>` | — | Other stdio MCP servers ([mcp.md](mcp.md#configuration)) |
 
 Sessions are stored as usual under `~/.volcanic/agent/sessions/telegram-<chatId>/`; after a restart each chat resumes
 its most recent conversation.
@@ -84,7 +87,7 @@ started a chat with the bot, Telegram refuses the message; the bot logs that and
 | `/help` | Short help |
 
 Any other `/command` is passed to the session, so extension commands such as `/claude-code-doctor` and
-`/claude-code-login` work.
+`/claude-code-login` work. `/mcp` lists the MCP servers (see [mcp.md](mcp.md#mcp)).
 When an extension asks something, the question appears with buttons (or as a reply prompt for free text).
 
 If the Claude subscription session behind the bot expires, the **first id in `AllowedUserIds`** (the bot owner)