SkillFoxx

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

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Starts a local proxy between Claude Code and the MCP server inside the 1C client
  • It only forwards requests and reconnects the session, actions in 1C are done by the server behind it
All reasons and checks
Russian stack

jimmo910/client_mcp_vanessa_proxyAuthor:Jimmo910

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/client-mcp-vanessa-proxy

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Starts a local proxy between Claude Code and the MCP server inside the 1C client
  • It only forwards requests and reconnects the session, actions in 1C are done by the server behind it

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 scenario

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

Limitations

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.

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.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A native component that runs a full MCP server inside 1C: tools, resources and prompts are written in BSL, while a DLL handles the protocol

MCP serverBroad access44
Russian stack

A Python proxy between an MCP client and a 1C HTTP service: reads metadata, object structure and predefined data, with optional OAuth2

MCP serverExtended access9
Russian stack

An MCP server that forwards questions, code review and code explanation requests to the 1C AI Assistant cloud service

MCP serverExtended access1
Russian stack

A thin stdio bridge for the iikona 1C extension: translates MCP over stdio into HTTP calls to a 1C service, connecting a 1C base to Claude Desktop and Cursor

MCP serverExtended access
Russian stack

A 1C extension with an MCP HTTP service plus a Python FastAPI proxy that adds stdio transport, OAuth2 and Docker deployment

MCP serverExtended access
Russian stack

A Go MCP proxy that dynamically turns any accounting system's HTTP service, including 1C, into a set of MCP tools without hand-writing a server

MCP serverExtended access

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.

README badge

Report a problem