SessionBridge: a temporary bridge to 1C over RDP
SessionBridge
A temporary MCP bridge to 1C over a client's RDP session with no infobase publishing: export, read and write through a tunnel that closes after the task
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Gives the agent read and write access to the client's 1C infobase through a temporary outbound tunnel
- The session token is passed manually and stays valid until the session is stopped
Install
Manual install
.\scripts\publish-agent.ps1Builds the self-contained SessionBridge.Agent.exe; the .NET 8 SDK is needed only on the build machine.
This is third-party code. Review the repository files before installing.
What it does
For the duration of a specific customization job, SessionBridge.Agent.exe is started on the client's machine over RDP, opening a local HTTP endpoint and a cloudflared tunnel out. On the developer's own machine, a Python server, Mcp/server.py, connects an MCP client such as Cursor to that tunnel using a session token. This replaces the manual cycle of exporting XML over RDP, copying it, and loading it back: the agent reads and writes straight through the bridge. When the task is done, the session and tunnel are stopped, with no need to publish the 1C infobase separately.
Who it is for. For 1C developers doing one-off customization work on client infobases over RDP who do not want to publish the infobase just for a single task.
Good fit when
- You need one-off customization on a client's infobase over RDP without publishing it permanently
- You are tired of the manual XML export, copy and reload cycle over RDP
- You work in Cursor and want dump, load, read, write straight through MCP
Not a fit when
- You need permanent access, not a one-off session for the duration of a task
- The client does not allow installing a third-party .exe and a cloudflared tunnel on their RDP
Example request
Connect to the client's infobase via SessionBridge and show the structure of the extension being customizedLimitations
Building the agent needs the .NET 8 SDK, though the ready Agent.exe is self-contained and needs no SDK on the client. The tunnel runs over cloudflared, so channel availability and stability depend on the client's network. The session token is passed manually between the agent window on RDP and the MCP config on the developer's machine, and the scheme is meant for a one-off session, not a permanent integration.
How to disable. Press STOP in the agent window on the RDP client, close the cloudflared tunnel with Ctrl+C, and remove the session-bridge entry from your MCP config.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| SESSION_BRIDGE_URL required | The cloudflared tunnel address opened by the agent on the client's RDP. |
| SESSION_BRIDGE_TOKEN required, secret | The session token issued by the agent window on start. |
Security check
- Gives the agent read and write access to the client's 1C infobase through a temporary outbound tunnel
- The session token is passed manually and stays valid until the session is stopped
README in short
The README describes a temporary AI bridge to 1C over a client's RDP with no infobase publishing, made of three parts: Agent.exe on the client, a cloudflared tunnel on the client, and a Python MCP server on the developer's machine. It covers building the agent with the .NET 8 SDK, a step-by-step client session with a token, configuring Cursor via mcp.json.example, and a table of MCP tools like bridge_status for checking the agent's and infobase's state.
FAQ
Does the client's 1C infobase need to be published?
No, that is the whole point of the bridge: no publishing is needed, access runs through a temporary tunnel for the session.
Does the bridge work only for specific subsystems?
No, the README notes it works for any customization job, not just particular subsystems.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Agent Skills for Google products
Agent Skills for Google products and technologies
Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring