SkillFoxx

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

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

Extended access

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
All reasons and checks
Russian stack

andromanpro/1c-ai-connector-mcp-proxyAuthor:Роман Андриянов

Install

Manual install

git clone https://github.com/andromanpro/1c-ai-connector-mcp-proxy.git
cd 1c-ai-connector-mcp-proxy
npm install
npm test

Installs from source, requires Node.js 18+.

Access and checks

How we review

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

  • 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

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 iikona

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.

Limitations

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.

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.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A stdio proxy between Claude Code and the client_mcp server inside 1C that reconnects itself after 1C restarts without a manual /mcp

MCP serverExtended access
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

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
Russian stack

A Docker gateway with one address instead of several MCP connections: 1C data, BSL navigation, ITS search via 1C:Napparnik, and a web dashboard

MCP serverBroad access5
Russian stack

A Docker gateway with 40-plus MCP tools for 1C, one address, a settings dashboard and a set of 1C skills for Claude Code

MCP serverBroad access

IIkona (1c-ai-connector)

ИИкона (1c-ai-connector)

Russian stack

A 1C extension with an LLM connector, agent loop, RAG, error monitoring and an MCP server that exposes the infobase to external agents

MCP serverBroad access108

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.

README badge

Report a problem