Back to blog

Best AI Companion for Bitrix CMS: Connect Mia via MCP

en • 7/7/2026

Turn your Bitrix site into a conversational workspace. This guide shows how to connect Mia Handles to 1C-Bitrix via the hiweb.site_mcp module — install, configure bearer auth, and manage content from Telegram.

Best AI Companion for Bitrix CMS: Connect Mia via MCP

Best AI Companion for Bitrix CMS: Connect Mia via MCP

Bitrix Site Manager powers millions of enterprise sites worldwide — and with Model Context Protocol (MCP), it now talks directly to Mia, your personal AI secretary. In this guide, we will walk through the full setup: from installing the official MCP module to connecting it with your Mia chat.

Once connected, you can ask Mia to manage news, iblocks, users, orders, and more — all from a single Telegram conversation. No browser tabs, no admin panels, no context switching.

What is MCP and why should you care?

The Model Context Protocol is an open standard that lets AI agents communicate with external services through a structured, secure interface.

An MCP server exposes capabilities of a system. An MCP client (Mia) connects to that server and invokes those capabilities on your behalf.

For Bitrix site owners, this means you can do things like:

  • Ask Mia to publish news articles or update iblock entries
  • Search orders, customers, or products by criteria
  • Generate reports on sales, traffic, or content performance
  • Create users, assign roles, or manage permissions
  • Query analytics or pull performance metrics

All from a single Telegram chat.

Prerequisites

Before you begin, make sure you have:

  • A 1C-Bitrix site (licensed, with module installation enabled)
  • Admin access to install modules and configure settings
  • A Mia Handles account with at least a Standard plan (MCP connections require API access)
  • An SSL certificate on your Bitrix site (HTTPS is required for the MCP endpoint)

Step 1 — Install the hiweb.site_mcp module

The recommended module is hiweb.site_mcp from the Bitrix Marketplace. It provides the official MCP server implementation for Bitrix.

Marketplace link: https://marketplace.1c-bitrix.ru/hiweb.site_mcp

Note: The marketplace page is currently under construction but will be published soon. If you already have the module, skip to Step 2.

From your Bitrix admin panel:

  1. Go to Settings → Marketplace
  2. Search for hiweb.site_mcp or use the direct link above
  3. Install and activate the module
  4. After activation, navigate to Settings → Settings of the Site → MCP Server

There you will find:

  • Endpoint URL — the public URL for the MCP endpoint (typically https://yoursite.com/api/mcp/)
  • Authentication — bearer token configuration
  • Tools to expose — toggle which Bitrix capabilities Mia can access (iblocks, news, users, orders, analytics, etc.)

Step 2 — Generate a Bearer Token

The Bitrix MCP module uses Bearer token authentication for secure API access.

  1. Go to Settings → Settings of the Site → MCP Server
  2. Click Generate Token or Create New Token
  3. Give it a name, for example Mia MCP Integration
  4. Set the token expiration (recommended: no expiration for production use)
  5. Copy the generated token — you will only see it once

This token becomes the credential Mia uses to connect to your Bitrix site.

Step 3 — Expose the endpoint securely

The MCP endpoint should only be reachable for services you trust. Typical options:

  • Bearer token auth — every request must carry the Authorization header with the bearer token
  • IP allowlist — restrict the MCP path to Mia's backend IP range
  • Private network / VPC — for enterprise setups

If your Bitrix site is behind Cloudflare or another WAF, make sure the MCP path is allowed through with POST methods. Test the endpoint first with curl (see Step 5) before connecting Mia.

Step 4 — Connect the Bitrix server in Mia Handles

Now the fun part. In your Mia chat:

  1. Open the Mia miniapp (tap your profile picture or use the menu)
  2. Go to Settings → Tools → MCP Servers → Add (or edit an existing server)
  3. Fill in the connection form:
Server name:   My Bitrix Site
Endpoint URL:  https://example.com/hiweb-site-mcp/
Transport:     JSON POST (stateless)
Auth:          Bearer token
Token:         (paste the generated bearer token)

Important: Select JSON POST (stateless) as the transport type. Do NOT use Streamable HTTP or SSE — the Bitrix MCP module accepts only POST JSON-RPC requests.

  1. Tap Connect. Mia will validate the endpoint, list available tools, and add the server to your chat.

Step 5 — Test the connection

Once connected, try a simple command in your Mia chat:

"List the last 5 news items on my Bitrix site"

Mia should return a summary pulled directly from your site. If you get an error, check:

  • Bearer token validity and expiration
  • MCP module is active and tools are enabled
  • Endpoint URL is reachable from Mia's backend (firewall, SSL certificate)
  • Transport type is set to JSON POST (stateless)

You can also test manually with curl:

curl -H "Authorization: Bearer YOUR_TOKEN" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}' \
  "https://example.com/hiweb-site-mcp/"

You should get a JSON tool list back — that means the server is alive.

Step 6 — What you can do after setup

Once connected, Mia becomes your co-pilot for Bitrix. Here are the most common things you can do:

  • Content operations — create, update, or publish news articles and iblock entries
  • Media management — list, upload, or replace images in files
  • User management — create accounts, reset passwords, assign roles
  • Orders & CRM — query orders, customers, deals, or leads
  • Analytics — pull traffic reports, conversion metrics, or sales summaries
  • Scheduled publishing — queue content for future dates via Mia's calendar

And because Mia already knows your calendar, tasks, and files, she can orchestrate Bitrix work alongside the rest of your day — for example:

"Create a news post about the product launch I sent you, schedule it for Wednesday at 14:00, and add a task for the marketing team to review it."

Mia will handle all three in one go.

Troubleshooting

Symptom Likely cause Fix
"Connection failed" Endpoint blocked or wrong URL Check firewall rules and SSL cert
"No tools available" Module disabled or no tools toggled Re-enable and select at least one tool
"Unauthorized" Invalid bearer token Regenerate in MCP settings and update in Mia
"HTTP 404" Wrong endpoint path Verify the module's configured endpoint URL
"Transport error" Wrong transport type Use JSON POST (stateless), not SSE or Streamable
Slow responses Too many tools enabled Disable unused tools, enable pagination

WordPress and Drupal work the same way

If you also run a WordPress or Drupal site, the same pattern applies. Each CMS has its own MCP adapter, but the connection workflow in Mia is identical — install the module, expose an endpoint, paste credentials into Mia. You can even connect all three platforms to the same Mia chat, and she will address each by name.

For the other guides, see:

Wrapping up

Connecting Bitrix to Mia via MCP turns your CMS from a standalone dashboard into a conversational extension of your daily workflow. Once set up, it just works — quietly, in the background, whenever you need it.

If you have questions or want help setting it up, just ask Mia directly in chat. She already knows the protocol.