Reconnecting proxy for the 1C client MCP
client_mcp_vanessa_proxy
A stdio proxy between Claude Code and the client_mcp server inside 1C that reconnects itself after 1C restarts without a manual /mcp
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only proxies JSON-RPC between Claude Code and an already configured 1C MCP server; it does not perform any actions in 1C itself
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/client-mcp-vanessa-proxyDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Assembled automatically, review before installing.
Run in a terminal
claude mcp add --transport stdio vanessa -- uvx run --script '/путь/к/mcp-proxy-reconnect.py'Or add to the file .mcp.json, in the project
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"vanessa","type":"stdio","command":"uvx","args":["run","--script","/путь/к/mcp-proxy-reconnect.py"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"vanessa": {
"type": "stdio",
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add vanessa -- uvx run --script '/путь/к/mcp-proxy-reconnect.py'Or add to the file ~/.codex/config.toml, for all projects
[mcp_servers.vanessa]
command = "uvx"
args = ["run", "--script", "/путь/к/mcp-proxy-reconnect.py"]If the file already exists, append the block to the end.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"vanessa": {
"type": "local",
"command": [
"uvx",
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"vanessa": {
"command": "uvx",
"args": [
"run",
"--script",
"/путь/к/mcp-proxy-reconnect.py"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
MCP_BACKEND_URLoptional- URL MCP backend сервера, например http://localhost:9874/mcp
MCP_PROXY_LOGoptional- Путь к лог-файлу прокси
MCP_PROXY_WAIT_TOOLS_MINoptional- Минимальное количество инструментов для готовности backend
MCP_PROXY_WAIT_TOOLS_TIMEOUToptional- Таймаут ожидания регистрации инструментов backend
MCP_PROXY_INIT_PROBEoptional- Время ожидания ответа backend при старте перед offline-stub
MCP_PROXY_INIT_CACHEoptional- Путь к кэшу последнего успешного initialize
MCP_PROXY_TOOLS_CACHEoptional- Путь к кэшу последнего успешного tools/list
MCP_SERVER_LABELoptional- Имя сервера в offline-stub
MCP_START_HINToptional- Команда запуска 1С, которую прокси подсказывает при выключенной 1С
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Install uv, download mcp-proxy-reconnect.py from the Jimmo910/client_mcp_vanessa_proxy repository and add it to .mcp.json as a stdio server named vanessa with command set to the uv path and args ["run", "--script", "path/to/mcp-proxy-reconnect.py"], then start 1C with /C"runMcp;mcpPort=9874".
Other ways from the author
git clone https://github.com/Jimmo910/client_mcp_vanessa_proxy.gitOr grab just the file: wget https://raw.githubusercontent.com/Jimmo910/client_mcp_vanessa_proxy/main/mcp-proxy-reconnect.py. Requires uv to be installed.
This is third-party code. Review the repository files before installing.
What it does
The script sits between Claude Code and the MCP server that client_mcp (onec-client-mcp-devkit and compatible builds) runs inside the 1C client. The 1C client itself restarts many times per development session, and each restart kills the old Mcp-Session-Id; Claude Code does not reconnect on its own and needs a manual /mcp. The proxy catches that error, drops the stale session, resends a cached initialize and retries the original request with a fresh session id, so Claude Code always sees the server as connected. If 1C is not running when Claude Code starts, the proxy immediately returns a cached tool list instead of timing out, and a tool call gets a clear instruction on how to start 1C.
Who it is for. For 1C extension developers doing agentic work through the client-side MCP server who are tired of pressing /mcp after every restart.
Good fit when
- You develop a 1C extension with the client_mcp server and 1C restarts often
- You want Claude Code to stop asking for /mcp after every DESIGNER /LoadCfg
- You need a graceful start when 1C is not running yet at the beginning of a session
Not a fit when
- Your MCP backend is not client_mcp.cfe on the 1C port
- You need the 1C MCP server itself, not just a proxy in front of it
Example request
Connect to the 1C test client through vanessa and rerun the Vanessa Automation scenarioLimitations
The proxy only keeps the Claude Code session alive; the MCP server inside 1C still has to be client_mcp.cfe. A fully automatic cycle needs a client_mcp build from the master branch with dynamic tool registration, since 0.6.x releases only register Vanessa Automation tools after a manual click in the form. Backend state (an open feature, a connected TestClient) is lost on a 1C restart, and the agent may need to redo the connection steps. The author tested on macOS with 1C:Enterprise 8.3.27 and Vanessa Automation 1.2; other setups may need a different tool-wait threshold.
How to disable. Remove the vanessa entry from mcpServers in Claude Code's .mcp.json, or disable the server with /mcp.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| MCP_BACKEND_URL | Address of the 1C MCP backend, defaults to http://localhost:9874/mcp |
| MCP_START_HINT | The 1C startup command the proxy suggests to the agent when the database is off |
| MCP_PROXY_WAIT_TOOLS_TIMEOUT | How long to wait for the backend tools to register after a 1C restart, defaults to 120 seconds |
Security check
- Only proxies JSON-RPC between Claude Code and an already configured 1C MCP server; it does not perform any actions in 1C itself
README in short
The README explains the problem in detail: on restart, client_mcp.cfe issues a new Mcp-Session-Id, and Claude Code cannot reconnect on its own, so a dev session accumulates a dozen manual /mcp calls. It shows the proxy's flow, an offline stub for when 1C is off, a full table of environment variables with defaults, and a sample 1C startup script that waits for readiness via curl. It also explains the difference from the general-purpose mcp-proxy and notes the bug was filed as an issue upstream in onec-client-mcp-devkit.
FAQ
How is this different from sparfenyuk/mcp-proxy?
That general-purpose proxy does not handle HTTP 404 Session not found by reinitializing, it just forwards the error to the client. This proxy exists specifically to recover the session after a 1C restart.
Do I need to configure anything for a standard setup?
No, all environment variables are optional and assume a local 1C on port 9874; you only change them for a non-standard setup.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything