bitrix24

This Bitrix24 MCP Server provides a comprehensive integration layer for Bitrix24 CRM data. It exposes a suite of tools to manage contacts, deals, tasks, leads, companies, and users, along with utility and reporting capabilities. You can create, read, update, and list entities such as contacts, deals, tasks, leads, and more, and you can perform advanced searches and filtering across CRM entities. The server also includes utilities to validate webhooks, diagnose permissions, and monitor activities, making it suitable for AI agents to interact with a live Bitrix24 instance via MCP tooling. To use it, configure Claude Desktop or another MCP client to point at the Node.js server (via the command and path in your deployment) and supply the required environment variable for your Bitrix24 webhook URL. The tools are named with the bitrix24_ prefix, such as bitrix24_create_contact, bitrix24_get_contact, bitrix24_list_contacts, bitrix24_update_contact, and similarly for deals, tasks, leads, companies, and users, including enhanced deal filtering and various utility methods. When querying or performing actions, provide natural language prompts that map to these tool names and required fields (e.g., contact name, email, deal title, amount, and related IDs) to drive CRM operations via MCP.

Prerequisites:

• Node.js 18+ installed on your machine or server
• npm or yarn (as available)
• Access to a Bitrix24 webhook URL with appropriate permissions
• Git (optional, for cloning)

Setup steps:

1. Clone the repository (or download the source):

git clone <repository-url>
cd bitrix24-mcp-server

2. Install dependencies:

npm install

3. Configure environment:

cp .env.example .env
# Edit .env to set BITRIX24_WEBHOOK_URL and any other required settings

4. Build the project (if applicable):

npm run build

5. Start the MCP server locally:

npm start

6. Test the connection:

npm test

Notes:

• Ensure your Bitrix24 webhook URL is accessible from the server hosting the MCP server.
• If you deploy, update the Claude Desktop or MCP client configuration to point to the deployed server path (see Claude integration snippet in README).

Tips and considerations:

• Security: Keep your webhook URL secret and rotate regularly. Do not commit .env files to version control.
• Rate limiting: The client includes built-in rate limiting (2 requests/second) to respect Bitrix24 API limits; adjust usage patterns accordingly in your prompts to avoid throttling.
• Environment variables: You can add extra environment variables as needed (e.g., API keys, feature flags) and reference them in your runtime.
• Deployment: When deploying to production, ensure the server has a stable Node.js runtime, proper process management (e.g., PM2 or systemd), and TLS termination at the load balancer or reverse proxy.
• Extensibility: New tools can be added by updating src/tools/index.ts and corresponding handlers; re-build before deploying to ensure changes take effect.