MCP interface: Connecting AI assistants

Employees connect external AI assistants such as Claude, ChatGPT, or Copilot to your platform via the MCP interface. The assistant always acts on behalf of the person and with exactly their permissions. Conversely, Kai, the platform's AI assistant, can use tools from external services.

What is MCP?#

The Model Context Protocol (MCP) is an open standard that allows AI assistants to access other systems. Kibi Connect uses it in two ways:

• External assistants on your platform

  Claude, ChatGPT, Copilot, and other programs read content and act on behalf of a logged-in user—for example, searching wiki pages, creating tasks, or entering appointments.

• Kai with external tools

  Kai uses tools from external MCP servers, such as your ERP or CRM system, n8n, or Notion, without employees having to leave the platform.

Allowing External AI Assistants Access#

The MCP Server in Administration#

Open Administration → Integrations → MCP Servers. Only system admins can view and edit this page. It has four tabs:

• Overview

  Under Who can connect AI assistants?, you see which roles have the "Connect AI assistants via MCP" permission. You control this via roles; by default, only admins have it. Open Roles takes you directly to this permission in the role editor. Below that are the connection URL, which you share with your employees, and a brief explanation of how registration works.

• Connected Clients

  A table of all AI assistants accessing your platform: client name and address, usage (active accesses), and last access. Labels indicate whether a client is Verified: <Address> or uses an Unknown Domain. Clicking a row opens the details with all callback addresses. Use Revoke to end access.

• Security

  Here you specify which clients can newly connect (Allow only known clients), what happens with new AI assistants (Off, Notify only, or Admin approval required), and who gets notified. Under Requests, you see pending and rejected approval requests.

• Instructions & Technical Details

  Pre-written text for employees to copy into their AI chat—the assistant then guides them step-by-step through setup, including for Claude, Claude Code, Langdock, Microsoft Copilot Studio, and ChatGPT. Below that are the technical addresses (endpoints) in case a program asks for them.

On the "MCP Servers" card under Integrations → Overview, you also see for whom MCP applies: Active for: <Roles> or Not enabled for any role.

Who Can Connect AI Assistants#

Whether a person can connect AI assistants is determined solely by their role. The permission is called "Connect AI assistants via MCP" and is found in the role editor under Administration → Roles & Permissions in the System tab, under the AI Assistants (MCP) section.

• Default

  Only the System Admin role has this permission. To enable it for other roles, activate it in the role editor, for example via Open Roles in the Overview tab.

• Guests

  Guests can never connect AI assistants, even with a role.

• Without the permission

  The person does not see an AI Assistants (MCP) section in their profile. If they still try to connect, the consent page shows: "Connecting AI assistants is not enabled for your account. Contact your administration." No approval request is created for the administration.

• Permission revoked

  If a person loses the permission, the platform immediately blocks their existing connections. If they regain it, the connections work again.

• Existing platforms

  The previous setting has been adopted: Wherever MCP was enabled, System Admins have the permission. You can enable it for other roles in the role editor.

Completely Disable MCP#

To completely disable the interface, remove the "Connect AI assistants via MCP" permission from all roles—exceptionally, including the System Admin role. If no role has this permission, no AI assistant can find the interface: registration and login respond with "not found" (404), and connected assistants lose access.

Security: Which Assistants Can Connect#

Who can connect is controlled by roles. Under Security, you specify what can connect: Any AI assistant with an HTTPS address can self-register with your platform (Dynamic Client Registration). However, it only gets access when a person with the "Connect AI assistants via MCP" permission logs in and explicitly consents on the consent page. There, they see what the assistant can read and do on their behalf and where the access is going.

Assistants that identify themselves via a client metadata document—such as Claude, ChatGPT, and VS Code—appear as Verified, both on the consent page and under Connected Clients.

Allow Only Known Clients#

Under Security, you can restrict new connections to a list of domains. The list is pre-populated with known clients—Claude, ChatGPT, Cursor, Langdock, and Microsoft Copilot Studio—and can be edited: remove entries or add your own domains (only the address with https://, no path, e.g., https://app.example.com). Use Restore default list to revert to the pre-populated list.

• Assistants on your own computer

  Programs like Claude Code that run on the user's computer remain allowed even with the restriction enabled.

• Existing connections

  Enabling the restriction does not revoke anything. Therefore, check under Connected Clients if anything is listed that is not on the list and revoke it if necessary.

New AI Assistants: Notify or Approve#

Under Security, in the New AI Assistants card, you specify what happens when someone connects an AI assistant for the first time:

• Off

  No notification. Each person confirms the connection themselves.

• Notify only

  The administration receives a notification as soon as someone connects an AI assistant for the first time. This way, unwanted access is quickly noticed and can be revoked.

• Admin approval required

  A new AI assistant only gets access after the administration approves it. The person waits until then. Assistants on the list of allowed clients are already approved. As long as "Allow only known clients" is enabled, this option is grayed out—only what is on the list can connect anyway.

Below that, under Who gets notified (and approves)?, you choose either All Admins or Specific Admins—one or more people with the System Administrator role. If none of the selected people are admins anymore, notifications and requests go back to all admins.

How Approval Works#

• Approve previously denied requests

  Under Security → Requests, you see pending and denied requests. A denied request can be approved retroactively there with Approve Anyway.

• Assistants on your own computer

  Local assistants like Claude Code or programs in the development environment (IDE) do not require approval.

• Existing connections

  If you enable approval, existing connections remain valid.

Connecting Assistants (Guide for Employees)#

There is no API key or password to share. Each person connects their assistant themselves:

If the administration has enabled approval for new AI assistants and the assistant is not yet approved, a waiting page appears after login. Keep the window open—once approved, it continues automatically. If you close it, you’ll receive a notification and can simply reconnect the assistant after approval.

Your Assistants in Your Profile#

In your profile, under the Integrations tab, there is a section called AI Assistants (MCP), between "Devices and Apps" and "API." It is only visible if one of your roles has the "Connect AI assistants via MCP" permission. If nothing else appears in the Integrations tab, the tab itself is also missing without the permission. The section contains:

• Connection URL

  The address to enter in the AI assistant, with a copy button, and a brief explanation of how the connection works.

• Instructions for your AI assistant

  Text to copy: paste into the AI chat, and the assistant will guide you step-by-step through the setup.

• Your AI Assistants

  Your own connections with name, redirect address, label (verified, known, or unknown client), "Connected since," and last access. Clicking an entry opens the details. If admin approval is enabled, your own requests also appear here: Waiting for approval, Not approved (with reason, if provided), or Approved – reconnect now.

• Disconnect

  Immediately ends the assistant's access to your content. This only affects your own connection: colleagues using the same assistant remain connected. To reconnect, log in again with the assistant.

Setup per Program#

Replace <your-platform> with your platform's address. The exact connection URL is in the Overview tab and in your profile under Integrations → AI Assistants (MCP).

• Claude (claude.ai or Claude Desktop)

  Settings → Connectors → Add custom connector. URL: https://<your-platform>.kibi.de/api/mcp. Then select "Connect" and log in via the browser.

• Claude Code

  In the terminal, run claude mcp add --transport http kibi https://<your-platform>.kibi.de/api/mcp, then in Claude Code, call /mcp and start the login.

• Langdock

  In the Langdock workspace, under Integrations, add your own MCP server, enter URL https://<your-platform>.kibi.de/api/mcp, select authentication "OAuth 2.0 (Dynamic Client Registration)," then connect and log in via the browser.

• Microsoft Copilot Studio

  In the agent, under Tools, add a new tool of type "Model Context Protocol," enter the server URL, select authentication "OAuth 2.0" with dynamic discovery, then create the connection and log in via the browser.

• ChatGPT and other programs

  Create an MCP server of type "Streamable HTTP" with the connection URL and "OAuth" login.

Logging and Revocation#

• Logging

  Every call from an external assistant is logged.

• Connected Clients

  The Connected Clients tab shows for each client: name and address, whether it is verified or uses an unknown domain, active accesses, and last access. The details show all callback addresses.

• Revoke

  Immediately ends a client's access; all its accesses become invalid. The assistant must reconnect afterward. Without revocation, access is valid for 365 days.

• Disconnect in profile

  Each person can disconnect their own connection in their profile under Integrations → AI Assistants (MCP). Other people using the same assistant remain connected.

Extending Kai with External Tools#

You connect external MCP servers as connections: Administration → Integrations → Third-Party Systems, Connectors tab.

With Allow Personal Connectors, employees can additionally connect their own MCP servers to Kai for personal use. Such connections are only visible to the respective person.

Frequently Asked Questions#

• Why can't I connect an AI assistant?

  Probably none of your roles have the "Connect AI assistants via MCP" permission. In that case, the consent page shows: "Connecting AI assistants is not enabled for your account. Contact your administration," and the AI Assistants (MCP) section is missing from your profile. By default, only System Admins have this permission; the administration can grant it to other roles.

• What data does an external AI assistant see?

  Only what the logged-in person is allowed to see, and only from modules that are active on your platform.

• Can I block individual tools for external assistants?

  No, this option no longer exists. You control access via the users' permissions and active modules—or remove the "Connect AI assistants via MCP" permission from all roles.

• What does the yellow warning on the consent page mean?

  The application is not a known client. Only allow access if you set up the connection yourself. To exclude this entirely, enable "Allow only known clients" under Security.

• Can I review new AI assistants beforehand?

  Yes. Under Integrations → MCP Servers → Security, set the option "Admin approval required" for "New AI Assistants." A new assistant will then only get access after an admin approves it.

• How do I revoke an assistant's access?

  Under Integrations → MCP Servers in the Connected Clients tab, click "Revoke" for the client. Each person can also disconnect their own assistant: in their profile under Integrations → AI Assistants (MCP), click "Disconnect."

• What does the MCP interface cost?

  It is part of Kibi Connect. External services you connect may have their own costs.

• How do I completely disable MCP?

  Remove the "Connect AI assistants via MCP" permission from all roles, including the System Admin role—exceptionally, this is allowed for this permission. Afterward, no AI assistant can find the interface; connected assistants immediately lose access. Warning: "Reset to default" for the System Admin role restores the permission.