MCPGoProxy: a Go proxy for 1C and other ERPs
MCPGoProxy
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
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- The proxy forwards LLM client calls into the connected system's business logic, including 1C
- Disabling the localhost check via disable_localhost_protection widens network exposure
Install
- Works in
- Services
Manual install
mcp_server.exe --stdioRuns the proxy in STDIO mode for local MCP clients; config.json must sit next to the executable.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The proxy forwards LLM client calls into the connected system's business logic, including 1C
- Disabling the localhost check via disable_localhost_protection widens network exposure
This is third-party code. Review the repository files before installing.
What it does
The proxy acts as an intermediate MCP server between an LLM client and an arbitrary information system. The system publishes two HTTP endpoints: erp_tool_url returns the list of available tools with descriptions, and erp_call_url executes a specific tool call. MCPGoProxy dynamically builds the MCP inputSchema from that description, including nested objects and arrays, and forwards calls over HTTP with an Authorization header and mandatory ERP_API_KEY checking. It runs in two transport modes: STDIO for local clients like LM Studio, Cursor or Claude, and Streamable HTTP for clients like Open WebUI.
Who it is for. For developers of 1C and other accounting systems who want to give an LLM client access to their HTTP services without writing a separate MCP server for each model.
Good fit when
- The system already has an HTTP service with business logic and data, but no MCP wrapper
- You need both STDIO and Streamable HTTP client support from one proxy
- You want the tool set to be built dynamically on the ERP side rather than hardcoded in the proxy
Not a fit when
- The system cannot implement the two simple HTTP endpoints for tool description and calls
- You need a ready-made 1C tool set out of the box: this proxy only bridges protocols, you write the business logic yourself
Example request
Connect MCPGoProxy to the 1C HTTP service and show which tools it exposes via erp_tool_urlMCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
ERP_API_KEYrequired, secret- Key for mandatory authentication of the proxy's requests to the ERP HTTP service.
Limitations
The proxy ships no ready-made 1C tools; it is a universal bridge, and both HTTP endpoints plus the business logic need to be implemented on your own system. The localhost check can be disabled with disable_localhost_protection, which is worth doing carefully, especially in Docker setups. ERP_API_KEY authentication is mandatory, and calls to the ERP fail without it.
How to disable. Stop the mcp_server.exe process and remove the proxy entry from your MCP client config.
FAQ
Do I need to write MCP tools by hand?
No, the proxy builds the MCP inputSchema itself from the description your system's erp_tool_url returns.
What port is used in HTTP mode?
40242 by default, set in config.json via the http_host and http_port parameters.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA Go MCP gateway between an agent and a 1C HTTP service: references, sales, stock, cash and settlement reporting across several databases
1C metadata MCP proxy (adapted fork)
1C_MCP_SERVER_OWN
A Python proxy between an MCP client and a 1C HTTP service: reads metadata, object structure and predefined data, with optional OAuth2
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
A Go MCP server for debugging 1C over the HTTP Debug Protocol: breakpoints, step execution and variable inspection
A 1C external data processor with MCP and REST API: queries, metadata, event log and code execution without changing the configuration
A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL
README in short
The README explains the proxy's role as a bridge between LLM clients and an arbitrary information system, without tying it to a specific model. It covers two transports, STDIO and Streamable HTTP, the config.json format with erp_tool_url, erp_call_url, http_host, http_port and disable_localhost_protection, mandatory ERP_API_KEY authentication, and passing ERP authorization through the Authorization header.