Feature Wiki

Information about planned and released features

Tabs

(Project) Model Context Protocol Support

This is a project page that bundles several feature wiki pages which belong to a larger development activity for the ILIAS component [[]].

1 Aim of Project

The Model Context Protocol is an open, standardised communication mechanism that enables AI models to access external data and functions in a secure and structured manner.

By supporting MPC in ILIAS, we are opening up the platform for connections to AI models and applications, enabling more reporting and evaluation options without tying ourselves to specific services. For the many cases of specialised plugins and components, MPC can provide the basis for interacting with ILIAS.

  • Standardised AI interface: ILIAS can connect directly to any MCP-compatible AI clients (e.g. OpenAI, Anthropic, GitHub Copilot, LM Studio) – without proprietary APIs.
  • Less integration effort: Instead of maintaining a separate interface for each AI platform, all you need to do is implement an MCP server.
  • Longevity: MCP is supported by major players (Anthropic, OpenAI, Microsoft) and is establishing itself as the de facto standard for AI context integration – comparable to LTI in the education sector.

A key argument in favour of MCP in the learning management environment is the clear separation between the AI model and confidential learning or personal data.

  • MCP allows finely controlled access: the model only receives defined information (‘context resources’), not unrestricted data.
  • Data remains under internal control – no external API transfer of sensitive user data unless a component provides it.
  • Communication is transparent and traceable, which complies with legal requirements (e.g. GDPR, higher education law).

This allows institutions to use AI functions in ILIAS without having to rely on cloud APIs or insecure integrations.

With MCP, ILIAS can offer AI-supported functions that respond directly to course and usage data – context-sensitive, personalised and explainable.

  • Intelligent tutors: The model can access course content, learning progress or forum discussions via MCP and provide targeted support.
  • Automated feedback: For assignments or tests, the AI can generate feedback based on institutional assessment criteria.
  • Adaptive learning paths: The model can analyse learning behaviour and suggest resources or activities in ILIAS based on this analysis.

ILIAS and its components retain sovereignty over which data (including personal data) is made available.

The open source nature of MCP fits perfectly with the philosophy of ILIAS – open standards, transparency, interoperability. The implementation of MCP in ILIAS is a strategic step towards AI readiness for the system:
It enables secure, data protection-compliant and flexible AI integration, reduces integration costs, strengthens interoperability with modern AI tools and creates concrete added value for learners and teachers.

2 Possible risks

  • If too few components are integrated into ILIAS, an MCP server could be useless. Important components such as courses, learning progress, files, forums, online help, page editor, etc. would have to be adapted quickly to enable meaningful use.
  • MCP is a very new standard. It was only published by Anthropic at the end of 2024. Currently, it is the only standard of its kind, but it remains to be seen whether it will gain sufficient traction in the world of AI models. OpenAI officially adopted MCP in March 2025, and other providers have at least announced their intention to do so.
  • The standard could change rapidly to keep pace with the fast developments in the world of AI. ILIAS must keep up with these changes as quickly as possible in order to stay competitive.
  • An MCP server also offers a new attack vector for ILIAS. For example, in April 2025, a security vulnerability relating to prompt injection became known.

3 Involved Authorities and Stakeholders

  • All authorities of ILIAS components are potentially involved.
  • The Technical-Board should have stakes in this.
  • All plugin maintainers should have stakes in this.
  • All users of ILIAS should have stakes in this.

4 Timeline

ILIAS 12

  • Developer-Workshops to define the Interface for Internal Requests to Components
  • Defining the supported Scopes
  • Planning of the MPC-Server itself
  • Implementing first Adapters in Components

ILIAS 13ff

  • Providing more Adapters in Components

5 Related Feature Requests and Status

Feature Request

Suggested by

Funding

Planned Release

Status

6 Further Results

7 Additional Information

8 General Discussion

Please discuss specific questions of feature requests on the related feature wiki pages. This discussion section is only for a general discussion of the project and its realisation.

Technical Board, … :

UI-/UX-Experts, … :

Last edited: Yesterday, 11:13, Schmid, Fabian [fschmid]