iikona-mcp-proxy
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
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The execute_query tool can run queries against the 1C database via the extension's service
- The HTTP Basic password is stored in the MCP client's config
Install
Manual install
git clone https://github.com/andromanpro/1c-ai-connector-mcp-proxy.git
cd 1c-ai-connector-mcp-proxy
npm install
npm testInstalls from source, requires Node.js 18+.
This is third-party code. Review the repository files before installing.
What it does
The proxy solves one specific problem: the iikona extension runs an HTTPService with a runtime MCP service at /iikona-mcp/rpc inside a 1C database, but most MCP clients like Claude Desktop and Cursor only speak stdio. iikona-mcp-proxy is a thin Node.js go-between that accepts a standard MCP handshake over stdio and forwards calls as HTTP requests with Basic auth into 1C. Once connected, five tools become available in chat: ping, get_configuration_info, get_metadata_tree, get_object_structure and execute_query. For debugging without an MCP client, a separate test-call.js CLI hits the same methods directly.
Who it is for. For users of the iikona 1C extension who need to connect its runtime MCP service to Claude Desktop, Cursor or another stdio client.
Good fit when
- Your 1C database has the iikona extension (1c-ai-connector) installed with its HTTPService enabled
- Your MCP client only supports stdio transport, while the 1C service is only reachable over HTTP
- You need to debug calls to the 1C service without a full MCP client
Not a fit when
- The iikona extension (1c-ai-connector) is not installed: the proxy is useless without it
- Your MCP client can connect directly over HTTP: no go-between is needed
Example request
Show the database metadata tree via iikonaLimitations
Only works together with the separate 1c-ai-connector extension, which is not part of this repo. As of the README, npm publication was not finished, with the package expected via npx, so installing from source is currently required. A simple echo-into-stdin check does not work: the client must perform a full MCP handshake.
How to disable. Remove the iikona entry from the MCP client config, for example from claude_desktop_config.json.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| IIKONA_MCP_URL required | The URL of the 1C HTTPService's JSON-RPC endpoint. |
| IIKONA_MCP_USER required | The username for HTTP Basic authorization. |
| IIKONA_MCP_PASS required, secret | The password for HTTP Basic authorization. |
| IIKONA_MCP_TIMEOUT_MS | The HTTP request timeout in milliseconds. |
Security check
- The execute_query tool can run queries against the 1C database via the extension's service
- The HTTP Basic password is stored in the MCP client's config
README in short
The README describes the proxy as a stdio-HTTP go-between for the iikona extension's runtime MCP service, gives npm install steps and a planned npx option, a table of environment variables (URL, login, password, timeout), a Claude Desktop config, and a list of the five available tools. It separately explains why a simple echo-into-stdin check does not work and gives an internal CLI for a smoke test. It shows the flow architecture diagram and lists related repos: the extension itself, YAxUnit tests and a user guide. MIT license.
FAQ
Do I need this proxy if the 1C service already speaks HTTP?
Yes, if your MCP client only speaks stdio, like Claude Desktop and Cursor, the proxy is needed as a translator between stdio and HTTP.
How do I test the 1C service without an MCP client?
With the node tools/test-call.js utility and methods like ping or tools/call get_configuration_info, using the same environment variables.
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