Bitrix24

io.github.bitrix24Published by GitHub account bitrix24v1.0.0Updated Oct 24, 2026

MCP server enabling AI agents to manage Bitrix24 features via standardized protocol

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an AI agent manage Bitrix24 features through the standardized protocol.

What you can do
It connects an assistant to Bitrix24 over a remote streamable HTTP endpoint so the agent can manage Bitrix24 features through the standardized MCP protocol. The manifest does not list individual tools, so the exact set of supported actions is not documented here.
When to use it
Worth considering when you already use Bitrix24 and want an AI assistant to work with its features directly, rather than copying data between systems by hand.
Requirements
A remote endpoint at mcp.bitrix24.com; no local package or runtime is needed. Authentication is OAuth and is required, so you need a Bitrix24 account and must complete the OAuth authorization flow.
Before you install
Access is granted through OAuth, so the assistant acts with the permissions you authorize on your Bitrix24 account. Because the tool list is not published, confirm which actions it can take, especially any that change or delete data, before granting access.

Installation

In SourceWeft

  1. Open Bitrix24 in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.bitrix24%2Fbitrix24/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bitrix24": {
      "type": "http",
      "url": "https://mcp.bitrix24.com/mcp/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.