Bitrix24 patient booking MCP
Bitrix24 MedPro MCP
A narrow FastMCP server that creates a Bitrix24 CRM contact and lead for a doctor's appointment after the booking itself is confirmed elsewhere
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- It creates contacts and leads with patient personal data in the CRM
- The write-capable webhook is stored only in an environment variable
Install
- Works in
- Services
Manual install
pip install -r requirements.txt && BITRIX_WEBHOOK_URL=https://<portal>.bitrix24.ru/rest/<user>/<token> python server.pyBefore running, replace the appointment-date custom field in the code with one from your own portal.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- It creates contacts and leads with patient personal data in the CRM
- The write-capable webhook is stored only in an environment variable
This is third-party code. Review the repository files before installing.
What it does
The FastMCP-based Streamable HTTP server offers only two tools: create_contact sets up a patient card by name and phone, and create_lead creates a lead for a doctor's appointment with a date, time and a link to the already-created contact, writing the time into a portal-specific CRM custom field. The docstrings show the tools are meant to run right after a successful bookAppointment call from an external booking system that is not part of this repository. A separate /health endpoint confirms the service is alive.
Who it is for. As an example: for Bitrix24-based clinics that create a patient card and a lead after a booking already confirmed in an external system.
Good fit when
- You want an example of creating a CRM contact and appointment lead
- You have your own booking system and only need to push the result into Bitrix24
- Two tools with no CRM read access are enough
Not a fit when
- You need to read deals, search patients or run other CRM operations
- You have no booking system that calls bookAppointment before this server
- You need portal-configurable fields without editing code
Example request
Create a contact for patient Ivan Ivanov and open a lead for an appointment on April 24 at 11:00MCP
- Transport
- http
- Authentication
- API key
Environment variables
BITRIX_WEBHOOK_URLrequired, secret- Bitrix24 portal inbound webhook URL with crm permissions
Limitations
There are only two tools, contact and lead creation, with no reading, updating or cancelling. The UF_CRM_1776790754 custom field for the appointment date and time is hardcoded for the author's specific portal and must be changed in code for any other one. There is no README or license, and the tool was clearly built for one medical project, expecting an external booking system that is not part of this repository.
How to disable. Stop the server process and remove it from your MCP client config.
FAQ
Does the server book the appointment itself?
No, it only creates a CRM contact and lead after the booking is confirmed by a separate external system.
Will the custom field work for my portal?
Not directly: the code references a specific field ID from the author's own portal, which needs replacing with your own.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsAn MCP server for Bitrix24 CRM contacts and deals via an inbound webhook: search, lists and deal stage changes
Bitrix24 MCP Server (gunnit)
Bitrix24 MCP Server
A TypeScript MCP server for Bitrix24 CRM: contacts, companies, leads, deals, tasks and sales rep performance reports
Bitrix24 MCP by Bit2Beat
Bitrix24 MCP Server
Bitrix24 MCP server over an inbound webhook: CRM, tasks, disk, calendar, chat, business processes and config migration between portals
MCP server for Bitrix24 CRM analytics: deals, leads, contacts, tasks, manager activity and deals at risk
A read and write MCP server for the Bitrix24 REST API: CRM, tasks, scrum, calendar, disk, messaging and portal events
Bitrix24 MCP server with real calls
MCP Server for Bitrix24
A Bitrix24 MCP server with 43 tools and about 870 actions that executes real REST API calls instead of just serving documentation
README in short
There is no separate README in the repository. The single server.py file, built on FastMCP, declares two tools with detailed English docstrings explaining the call order after an external bookAppointment, handles Bitrix24 errors via httpx, and exposes /health to check the service is alive.