Skip to content
Kibi Connect
Manual Kibi Connect

MCP interface: Connecting AI assistants

5min

The MCP interface connects external AI assistants such as Claude, ChatGPT, or Copilot with your Kibi Connect platform—and expands Kai, the integrated AI assistant, with tools from services you already trust. This area is exclusively available to system administrators.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI assistants to access external systems in a standardized way. Kibi Connect uses MCP in two directions:

  • External assistants on your platform: Assistants like Claude (Anthropic), ChatGPT (OpenAI), or Copilot (Microsoft) access shared content on behalf of a logged-in user—such as wiki pages, tasks, or calendar entries. Access is limited to the user's permissions and requires their explicit consent.

  • Kai with external tools: Kai, the integrated AI assistant, can use additional tools via external MCP servers—for example, to retrieve data from an ERP or CRM system, trigger n8n automations, or integrate services like Notion without users having to leave the platform.

MCP does not replace manual integrations but complements them: The standard is designed so that AI assistants act in context—always on behalf of a person, never independently.

Prerequisites

MCP features are enabled by Weslink per platform. Contact your Weslink representative if you want to activate MCP.

After activation, system administrators can find all settings under: Administration → top AI bar → "MCP" tab

Allowing External AI Assistants to Access

This section describes how to allow external assistants like Claude, ChatGPT, or Copilot to access your platform. The relevant settings are located in the sub-tab "Access (Incoming)" within the MCP tab.

Enable MCP Access

  1. Open Administration → top AI bar → "MCP" tab → sub-tab "Access (Incoming)".

  2. Enable the toggle Enable MCP access.

  3. Under Tool Sharing, select the specific tools (e.g., searchWiki or createTask) that external assistants are allowed to use. A "Select All" checkbox allows you to easily enable or disable all tools at once. If all are selected, any newly added tools will automatically be enabled as well.

  4. The displayed connection URL must be entered by your employees into their respective assistants. It remains constant—employees only need to enter it once.

Screenshot: Sub-tab "Access (Incoming)" with toggle, connection URL, and tool sharing (image to be added manually)

Connecting Assistants (Guide for Employees)

Each person connects the assistant themselves with their own account. Share the connection URL and the following instructions with your employees:

  • Claude (Anthropic): Settings → Connectors → Custom Connector → Enter URL.

  • ChatGPT (OpenAI): Settings → Connected apps → New Integration → Enter URL.

  • Copilot (Microsoft): Copilot Studio → Add Connector → MCP → Enter URL.

After entering the URL, the assistant redirects to your platform's login page. After logging in, a consent page appears, displaying the requested tools and the redirect destination (e.g., claude.ai). Tools not enabled by the administration are grayed out and marked with "blocked by your administration." Access is granted only after confirmation.

Screenshot: Consent page when connecting an AI assistant (image to be added manually)

Important: Access always occurs on behalf of the logged-in user and with their permissions—an external assistant never sees more than the user themselves can see in the platform. The tool sharing settings in the administration further restrict access: No user can grant access to tools that the administration has not enabled.

Managing and Revoking Incoming Connections

In the sub-tab Incoming Connections, system administrators can see all active connections to the platform. For each connection, the following details are displayed: redirect domain, active accesses, "Used by" (on whose behalf the connection is active), and "Last Access."

Revocation is possible directly in the row. Clicking Revoke immediately terminates the assistant's access and invalidates all ongoing accesses for that connection. The assistant must then be reconnected.

Screenshot: Sub-tab "Incoming Connections" with connection list and revocation function (image to be added manually)

Expanding Kai with External Tools

External MCP servers provide Kai with additional tools. For example, Kai can retrieve entries from your ERP or CRM system, trigger n8n automations, query IoT interfaces, or integrate services like Notion—without employees having to leave the platform. All settings are located in the sub-tab "Outgoing Connections."

Creating an External MCP Server

  1. Open Administration → top AI bar → "MCP" tab → sub-tab "Outgoing Connections".

  2. Click New Server—a side window opens where you can create and edit the server.

  3. Fill in the following fields:

Field

Description

Name

Display name in the platform, e.g., "Notion"

Short Code

Short internal abbreviation (not displayed)

Server URL

HTTPS address of the MCP server

Authentication

None / Bearer Token / OAuth

Requested Permissions (Scopes)

For OAuth servers only: enter desired scopes. Leave blank = all scopes offered by the provider.

After saving, the platform automatically retrieves the available tools from the server and displays them in the side window.

For OAuth-based services, the action Connect appears after saving. Click it to complete authorization with the respective provider—you will be redirected to do so.

Screenshot: Sub-tab "Outgoing Connections" with server list and side window for creation (image to be added manually)

Consent Before Tool Use

For individual tools, you can specify that Kai must first obtain confirmation from the requesting person in the chat before each use. All other tools are available to Kai without prompting (default).

To do this, enable the option Ask before use for the desired tool in the tool list.

Tip: If you need different rules for different roles, create the same MCP server a second time with its own access control.

Restricting Access to Roles, Groups, or Individuals

Using the option Restrict Access, you can define who is allowed to use the tools of this server via Kai. Possible restrictions:

  • Roles (e.g., only system administrators)

  • Groups

  • Individuals

Without restrictions, all employees have access to the tools. Once at least one restriction is set, only the selected individuals have access.

Usage in Chat

Once an external MCP server is set up, its tools are automatically available to Kai in the chat. When Kai uses an external tool, this is made visible in the chat—so it is traceable which services contributed to a response.

Screenshot: Kai uses an external tool in the chat (image to be added manually)

Data Privacy: Requests to external MCP servers leave your platform. Only connect services that you and your employees trust. Every tool use is logged in the platform.

Frequently Asked Questions

What data does an external AI assistant see?

Only the content that has been enabled via Tool Sharing—and only within the permissions of the logged-in user. An external assistant can never see more than the person who connected it.

How do I revoke access for a person or assistant?

Open the sub-tab Incoming Connections and click Revoke for the desired connection. Access ends immediately, and all ongoing accesses for that connection become invalid.

What does the MCP interface cost?

The MCP interface is part of Kibi Connect and does not incur any separate fees. External services that you connect as MCP servers may have their own terms of use and costs.

Does MCP work with every AI assistant?

MCP is an open standard. Assistants that support MCP can be connected. Common examples include Claude (Anthropic), ChatGPT (OpenAI), and Copilot (Microsoft). Check the respective provider's documentation to see if an assistant supports MCP.

Can I deactivate the MCP interface?

Yes. Disable the toggle Enable MCP access in the sub-tab Access (Incoming). Existing connections will be immediately disconnected.