MCP interface (Additional module)

With the chargeable add-on module, an MCP interface can be set up in SmartProcess. MCP stands for Model Context Protocol and enables other AI systems to securely access SmartProcess content and integrate it into a central AI system within the company (e.g., a Copilot agent).

Setting up the MCP interface

If the module has been purchased, you’ll find the MCP Interface option under Settings --> Configure Application, where you can set the authentication method.

Under MCP Interface Authentication Mode, there are 3 options to choose from:

MCP Interface deactivated

In this case, the interface is inactive, so external AI agents cannot access SmartProcess content.

OAuth

In this case, a Microsoft Entra ID profile must be selected for authenticating the external AI system.

This profile must first be set up in the SmartProcess setting Directory services and single sign-on. For the AI agent to successfully connect to this interface, the data for the application ID, application secret etc. in its configuration must match the information in the Entra ID profile in SmartProcess.

If Entra ID is also used to log in SmartProcess users, the user can be uniquely identified by their username or email address when they make requests via the external AI agent.

This ensures that, in this case, each user’s individual access rights to processes, documents and wiki entries are taken into account for every request made via the AI agent.

API-Key

In this case, an API profile must be selected for authenticating the external AI system. This profile first needs to be set up in the corresponding SmartProcess settings.

If the API profile is to be used exclusively for authenticating the MCP interface and not for accessing the REST API for transaction data, catalog data, etc. the REST API add-on module is not required.

For the AI agent to connect successfully to this interface, the API key in its configuration must match the one displayed in SmartProcess when the API profile was initially created.

Because an API profile is always assigned to one specific SmartProcess user, this option cannot take individual access rights to processes, documents, and wiki entries into account.

Therefore, for any request made via the AI agent, the access rights of the user assigned to the API profile in SmartProcess are always applied - regardless of who formulates the request.

FAQ on the MCP Interface

What is the Model Context Protocol (MCP)?

MCP is a standard that enables AI systems to connect to applications and data sources. It provides a unified way to make information from a system available to AI agents in a structured format.

Why use an MCP interface?

MCP is a widely used standard for connecting various AI systems. With this interface, it is now possible to integrate content from SmartProcess into the company’s central AI system.

How can the MCP interface be connected?

An AI agent can be authenticated for SmartProcess via OAuth or an API key. The setup process is described above in the Setting up the MCP interface section.

Which AI systems can be used with the MCP interface?

Since MCP is a widely used standard, its use is not limited to specific AI systems. Therefore, SmartProcess can be integrated with any system, agent, or chatbot that is also MCP-compatible.

What SmartProcess content can be accessed via the MCP interface?

AI agents can access the same content via the MCP interface that SmartProcess’s internal SmartAI chatbot uses to answer user inquiries, namely:

- Published processes
- Published documents
- Entries in the Wiki menu

Relevant text passages from these entries are transmitted to answer user queries.

Are access rights to SmartProcess content taken into account?

Only if the external AI system is authenticated via OAuth, because in that case the requesting user can be uniquely identified and their individual read permissions can be taken into account.

When authenticating via API key, all requesting users are provided information on processes, documents, and wiki entries with identical read permissions, which depend on the user specified in the API profile configuration.

Details are described above in the section Setting up the MCP interface.

Setting up the MCP interface

FAQ on the MCP Interface

Contact