@itc27ru/bitrix-mcp-bridge
v0.1.0
Published
MCP bridge for citdigital.aimcptool Bitrix module
Downloads
195
Readme
@itc27ru/bitrix-mcp-bridge
MCP bridge for the Bitrix module cit_digital.ai_tool.
Primary launch mode is npm package execution via npx.
Requirements
- Node.js 20+
- Bitrix module endpoint and API token
Required env
BITRIX_BASE_URL=https://<site>/bitrix/tools/cit_digital.ai_tool/api/v1/index.php?op=BITRIX_API_TOKEN=<token>- Optional:
REQUEST_TIMEOUT_MS(default15000)LOG_LEVEL(trace|debug|info|warn|error|fatal, defaultinfo)
MCP client setup (recommended)
[mcp_servers.bitrix]
command = "npx"
args = ["-y", "@itc27ru/bitrix-mcp-bridge"]
[mcp_servers.bitrix.env]
BITRIX_BASE_URL = "https://example.com/bitrix/tools/cit_digital.ai_tool/api/v1/index.php?op="
BITRIX_API_TOKEN = "bxt_..."Fallback mode (run-url)
If needed, you can still launch a published single-file URL:
npx -y run-url https://itc27.ru/0mcp/bridge/bitrix-mcp-bridge.jsLocal development
cp .env.example .env
npm install
npm run devBuild single-file CLI
npm run build:bundleOutput file: bitrix-mcp-bridge.js (with shebang, ready for npm bin and run-url).
Smoke checks
Direct endpoint smoke:
npm run smokeMCP stdio handshake smoke:
npm run smoke:mcpRelease rules
- Bump version:
npm version patchornpm version minorornpm version major
- Publish scoped package as public:
npm publish --access publicNotes
- Existing MCP tool names and endpoint mapping remain backward-compatible.
- The bridge sends
Authorization: BearerandX-Api-Tokenheaders.
