This Article covers some best practices using Simplifier MCP Server

Restrict Access to a project

To focus work and keep it isolated from other parties that use the same instance, it makes sense to create a Simplifier project and work with a user account that is restricted to it.

The LLM will do all operations on behalf of the user of the given session token.

For minimum usage of the MCP, such an account needs:

• A Project Role on the intended Simplifier project. For instance, the predefined Pro_Developer role contains necessary permissions on Business Objects and Connectors.

• If the LLM should be able to query configured OAuth clients, additional permission on Server Settings with Authentication Settings characteristic is required.

Also, when working on a prompt, tell the LLM the working project and make it permanent, so that it will use it for creating new items.

Do not use it on production systems

Some functionality requires adjusting the default instance configuration in a way that one might not want to use on a production system.

Access Logs

Logging is restricted by default settings and will not produce the expected results. To let the LLM fetch logs also on successful requests, the log level on executions has to be changed to INFO first.

Please consider not doing it on production systems, because this will create a huge amount of log messages.