Bitrix24

Created By
Bitrix244 months ago
The Bitrix24 MCP Server is designed to connect external systems to Bitrix24. It provides AI agents with standardized access to Bitrix24 features and data via the Model Context Protocol (MCP). The MCP server enables external AI systems to interact with Bitrix24 modules through a single standardized interface. You can connect the Bitrix24 MCP Server to the AI model you already use and manage Bitrix24 directly from it. The MCP server allows actions to be performed and data to be retrieved strictly within the access rights configured in your Bitrix24: the AI agent receives only the information and capabilities that are explicitly requested and authorized. Interaction with the Tasks module is supported (the list of supported modules and available actions is gradually expanding).
Overview

Bitrix24 MCP Server

The Bitrix24 MCP Server is designed to connect external systems to Bitrix24. It provides AI agents with standardized access to Bitrix24 features and data via the Model Context Protocol (MCP).

The MCP server enables external AI systems to interact with Bitrix24 modules through a single standardized interface. You can connect the Bitrix24 MCP Server to the AI model you already use and manage your Bitrix24 directly from it.

Interaction with the Tasks module is supported, including task creation, changing task assignees, working with task descriptions, creating and sending messages to task chats, and other actions. The list of supported modules and available actions is gradually expanding.

The Bitrix24 MCP Server supports performing actions and retrieving data strictly within the access rights defined by your Bitrix24 administrators, the user, and Bitrix24 security policies. Each MCP request is processed in isolation: the AI agent receives only the information and capabilities that are explicitly requested and authorized. If the user controlling the AI agent does not have permission to perform certain actions in Bitrix24 or has not granted those permissions to the agent, the AI agent will not be able to execute them.

The MCP server is intended for intelligent Bitrix24 management scenarios from external AI systems, where AI agents perform actions in the system without direct user interaction with the interface.

Server Config

{
  "mcpServers": {
    "bitrix24": {
      "url": "https://mcp.bitrix24.com/mcp/",
      "timeout": 30000,
      "headers": {}
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
Bitrix24
Star
-
Language
-
License
-
Category
Homepage

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago
Alloy

2 days ago