AI Assistants & MCP

← Back to overview

FIND KNOWLEDGE | AI ASSISTANTS & MCP

With the Model Context Protocol (MCP), employees use KenCube directly from their AI assistant, such as Mistral, Claude, ChatGPT or their company's own AI platform. Every access runs on behalf of the person and only with their permissions in KenCube.

Easy to connect

• Sign-in in the browser via OAuth, no manual tokens
• Server address and quick guide for common assistants in "My Area"
• View and revoke your own connections at any time
• Also for company-owned AI platforms, for example with WebUI
• Access tokens for integrations and scripts, issued by administrators only

In practice: A company runs its own AI platform with a web interface for all employees and connects KenCube via MCP. Anyone who asks about the travel expense policy there gets the answer from KenCube. Only content the person is also allowed to read in KenCube is used.

What assistants can do in KenCube

• Find and read posts, documents and people
• Create and edit posts, in editorial workspaces only for approval
• Register for or cancel events, view open to-dos
• Read and create tickets, protocols and project tasks
• Maintain surveys, courses, shop items and tables, if enabled
• Send chat messages to colleagues

In practice: A project manager prepares the weekly report in her AI assistant. The assistant reads the open tasks from KenCube and summarizes them. After she confirms, it creates two new tasks in the project.

Security and control

• Always with the person's permissions, never beyond them
• Off by default, activated by administrators
• Access scopes as a default and per group, such as read and search only
• Restrict use to specific people and groups
• Confirmation before actions that change data, set centrally or per person
• Settings changes in the audit trail

In practice: IT first enables MCP for the management team with all access scopes, while the other groups may only read and search. If IT later blocks a scope, this applies immediately to all existing connections as well.

Required modules

Access via MCP is part of the add-on module AI Companion. Tools for tickets, protocols, projects, surveys or courses are also available when the respective add-on module is active: Self-Service with Ticket System, Compliance & Quality Management, Project Management or Onboarding & E‑Learning. All add-on modules can be added at any time and rolled out step by step.

← Back to overview | Next building block: Forms & Tickets