How to Connect ChatGPT, Claude or Manus to Bitrix24 via MCP

What MCP Is and Why Bitrix24 Supports It

Model Context Protocol (MCP) is an open standard that lets an AI agent receive a structured list of tools - functions it can call during a conversation - so it can act on real systems rather than just generate text.

Instead of a user copying data between a chat window and a CRM, an MCP-connected assistant can query, create, or update records directly. The AI receives a machine-readable description of available operations; every action it takes goes through the same permission layer as a normal human user.

Since 1 September 2026 the MCP server is part of the Vibe+ plans (per the official helpdesk). The result is that tools like ChatGPT, Manus, or Cursor can manage your portal from within their own chat interfaces - no middleware required.

What are the two Bitrix24 MCP endpoints and how do they differ?

Bitrix24 publishes two distinct MCP endpoints with entirely different purposes: one for managing your portal data, and one for accessing developer documentation - and mixing them up will waste significant setup time.

The portal-management server (the focus of this article) requires authentication and operates within the employee's own permission set. The developer-documentation server (apidocs.bitrix24.com) is public and gives AI coding tools such as Claude Code or Cursor access to the REST API reference - useful when building integrations, not for reading live data.

There is also a third tool for developers building Vibecode applications: the @bitrix24/mcp-vibecode-api npm package. It is covered briefly in the Vibecode MCP section below.

How an Administrator Enables the MCP Server

An account administrator must explicitly turn on MCP access before any external AI client can connect - by default it is off.

Steps:

1. Open the menu next to your account name.
2. Go to Settings > MCP servers.
3. Toggle Allow connection of external AIs to Bitrix24 to on.
4. Click Save.

Bitrix24 displays a warning at this step: "These connections may introduce security and data processing risks outside of Bitrix24's control." Read it, and review the security checklist below before proceeding.

The MCP server feature is part of the Vibe+ plan. Portals on Essentials plans do not have access to it (per helpdesk.bitrix24.com/open/26027119/).

Connecting ChatGPT via OAuth (Official)

ChatGPT connects to Bitrix24 via OAuth - the only officially documented method - and requires a ChatGPT Plus or Pro subscription.

Steps inside ChatGPT:

1. Open Settings > Apps and connectors > Advanced settings.
2. Enable Developer mode.
3. Click Create app and fill in: - Name: anything descriptive (e.g., "My Bitrix24") - MCP server URL: https://mcp.bitrix24.com/mcp/ - Authorization type: OAuth
4. Accept the prompts, then sign in to your Bitrix24 account when redirected.

Once connected, use the integration by clicking + > More > Bitrix24 in the ChatGPT message box. The AI will act on your portal with your own user permissions.

This is a fully official integration described in Bitrix24's own helpdesk documentation (helpdesk.bitrix24.com/open/25866707/).

Connecting Manus via Access Token (Official)

Manus connects using a static access token that you generate inside Bitrix24 - this method also works for any other client that supports custom MCP with a bearer token.

Steps in Bitrix24 to get the token:

1. Go to Applications > MCP connections.
2. Click Get connection token.
3. Copy the token.

Steps in Manus (or any compatible tool):

1. Add a custom MCP connector.
2. Set transport to HTTP.
3. Set URL to https://mcp.bitrix24.com/mcp/.
4. Set authorization method to Access token and paste the token.

This token-based approach is officially documented alongside ChatGPT and Manus as the two primary connection methods (helpdesk.bitrix24.com/open/25866707/).

To revoke access later, go to Applications > MCP connections > My tokens and click Close access. Note: any tasks, deals, or records created through the integration before revocation remain in the portal.

Connecting Claude, Cursor and Other Clients (Custom Setup)

Claude Desktop, Cursor, VS Code, and n8n can all connect to the Bitrix24 portal-management MCP server using the same token method described for Manus - but this is a custom setup, not an officially documented integration for those specific clients.

Bitrix24's overview article (helpdesk.bitrix24.com/open/25846367/, updated 5 August 2026) names Manus, Cursor, and n8n as example clients. If your client supports remote MCP with a header-based bearer token over HTTP (Streamable HTTP), the connection pattern is the same:

• Transport: HTTP
• URL: https://mcp.bitrix24.com/mcp/
• Auth header: your token from Applications > MCP connections

For Claude Code connecting to the developer documentation MCP (not portal data), the official command is:

claude mcp add --transport http b24-dev-mcp https://mcp-dev.bitrix24.com/mcp

That server provides API docs only - no live data, no authentication needed. For portal data, use the token approach above and confirm that your version of the Claude client supports remote MCP with a bearer header before treating it as a production setup.

AI Client Connection Methods at a Glance

External AI assistants connect to the Bitrix24 portal MCP server through either OAuth or a static access token, depending on what each client supports.

"Official" means Bitrix24's own helpdesk documentation describes that specific client by name. "Custom" means the generic token-over-HTTP method works if the client supports it, but Bitrix24 has not published a dedicated guide for that client.

What can the AI access and do in Bitrix24 via MCP?

The AI assistant performs actions in Bitrix24 only when an employee gives a command and only within that employee's own access permissions - it cannot exceed the rights of the account used to connect.

What the portal-management MCP server can do (as of August 2026):

• CRM: move deals, create pipelines, edit stages
• Tasks: find, create, edit, assign tasks and checklist items
• Company structure: read org chart, invite employees
• Email: find, read, and send emails
• Calendar: create events
• Communication: create chats and Feed posts from emails

What it cannot do: anything outside the connected user's role. A sales rep's token cannot access HR records if that rep does not have HR rights in Bitrix24. This boundary is enforced server-side.

For a broader look at how Bitrix24 handles AI data routing and compliance, see Where Bitrix24 AI Processes Your Data - and How to Stay Compliant.

What should you check before connecting an AI client to Bitrix24?

Connecting an external AI to a live CRM portal carries real risk. Bitrix24 acknowledges this in its own warning message. Run through this checklist before enabling production access.

• Enable MCP only on portals where it is needed. Do not enable it org-wide by default.
• Use a dedicated user account for token-based connections where possible, with the minimum permissions required for the use case.
• Treat the connection token like a password. Do not paste it in shared documents, chat logs, or version control.
• Verify the OAuth redirect when connecting ChatGPT: confirm you are signing in to your actual Bitrix24 domain, not a spoofed page.
• Test with read-only tasks first. Run a query that only fetches data before allowing any write operations.
• Audit connected tokens regularly. Go to Applications > MCP connections > My tokens and close any tokens that are no longer in use.
• Revoke immediately if a token is compromised. Records created before revocation remain; new write access stops.
• Inform your data protection officer if your portal stores personal data subject to local regulations (e.g., UAE PDPL, LGPD, or GDPR) before routing CRM data through a third-party AI service.
• Check your Bitrix24 plan includes Vibe+. The MCP server is not available on Essentials plans.

For a broader hardening guide, see Self-Hosted Bitrix24 Security Hardening: 25-Point Checklist.

Vibecode MCP for Developers: A Separate Tool

The @bitrix24/mcp-vibecode-api package is a separate developer tool for building Vibecode applications - it is not a substitute for the portal-management MCP server and targets a different audience entirely.

The Vibecode MCP connects AI coding tools (Claude Code, Claude Desktop, Cursor, Codex CLI) to the Vibe API using a vibe_api_ key rather than a portal user token. It is optimised for application development workflows: creating, publishing, and managing Vibecode apps, not for an employee managing CRM from a chat window.

The official connection command for Claude Code is:

claude mcp add vibecode -- mcp-vibe-api --key vibe_api_... --api-url https://vibecode.bitrix24.com

This tool is documented at vibecode.bitrix24.com/docs. If you are building a Vibecode application rather than managing a portal from a chat interface, this is the right starting point.

For context on what Vibecode is as a platform, see Bitrix24 VibeCode: Building Business Apps with AI Agents.

The MCP ecosystem around Bitrix24 is growing quickly. The MCP Hub for external services (Gmail, Google Drive) is announced as coming soon. If you need help planning an MCP-based workflow or reviewing security before rollout, the team at ACP Group - a Bitrix24 Gold partner - can help. Contact us via acp-24.com.