simplifier-mcp
# Simplifier MCP Server
Simplifier is the leading low-code platform in the SAP ecosystem. Build custom
apps in a full-stack low-code cloud development environment, reducing your
dependency on full-scale coding. Integrate with ERP, CRM and other systems
easily using standardised connectors.
Find more information in our [community](https://community.simplifier.io) or try
Simplifier [for free](https://community.simplifier.io/start-for-free).
---
This repository contains an MCP server (Model Context Protocol) that enables
integration of AI assistants with the **[Simplifier Low Code Platform](https://simplifier.io/platform/)**.
It provides tools and resources for creating and managing Simplifier Connectors and BusinessObjects.
## Overview
The Simplifier MCP Server allows to interact with a Simplifier instance to:
- **Manage Connectors and Logins**: Integration components that connect external systems
- **Manage Business Objects**: Server-side executed JavaScript functions for business logic
- **Manage Data Types**: Data structures for interacting with Connectors and internal objects
- **Execute Business Object Functions**: Run JavaScript functions with parameters and retrieve results
- **Execute Connector Calls**: Call external systems via Simplifier Connector
- **Access platform resources**: Browse connectors, business objects, and system information
### Supported Connector types
Currently only the following connector types are fully supported:
* REST
* SOAP
* SQL
* SAPRFC
* OData (proxy-only; does not support Connector Calls)
### Client compatibility
The Simplifier MCP server exposes its data through two parallel surfaces so that
every MCP client can use it in full, regardless of which parts of the MCP
protocol that client supports:
* Clients that implement MCP **Resources** (e.g. Claude Code, Claude Desktop,
MCP Inspector) can browse and read Simplifier data through
`simplifier://…` URIs — for example `simplifier://businessobjects`,
`simplifier://connector/{name}`, or `simplifier://documentation/…`.
* Clients that only implement MCP **Tools** (e.g. OpenCode, Cursor, Cline,
Continue, Windsurf) get equivalent read access through tools named
`*-list`, `*-get`, `documentation-get` and `connector-wizard-rfc-search`.
Both surfaces share the same underlying implementation, so behavior is
identical. Where both are available, clients should prefer resources.
## Usage
Check out [Simplifier Community Docs](https://community.simplifier.io/doc/current-release/extend/setup-mcp-to-interact-with-ai-models/)
on how to use and set up the MCP server best.
### Add the MCP to claude code ...
**Using node / npx:**
```
claude mcp add simplifier npx @simplifierag/simplifier-mcp@latest --env SIMPLIFIER_TOKEN=<your current simplifier token> --env SIMPLIFIER_BASE_URL=https://<yourinstance>-dev.simplifier.cloud
```
**Using Docker:**
```
claude mcp add simplifier-docker docker -- run --rm -i --env SIMPLIFIER_TOKEN=<your current simplifier token> --env SIMPLIFIER_BASE_URL=https://<yourinstance>-dev.simplifier.cloud simplifierag/simplifier-mcp:latest
```
If your Simplifier is hosted on premise, then the `SIMPLIFIER_BASE_URL` of your DEV instance will be different from the mentioned schema.
#### After a new login to Simplifier
With every login to Simplifier your SimplifierToken will change. So you will have to:
- exit your AI agent (in this example claude),
- then remove the configuration of the MCP
```
claude mcp remove simplifier
```
- and then add the MCP again with the new token (see upper command) and restart your AI agent
### ...or use this example configuration for claude code to use the MCP
e.g. in a file named .mcp.json placed in the directory, where claude is started.
**Using node / npx:**
```json
{
"mcpServers": {
"simplifier-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"@simplifierag/simplifier-mcp@latest"
],
"env": {
"SIMPLIFIER_BASE_URL": "https://<yourinstance>-dev.simplifier.cloud",
"SIMPLIFIER_TOKEN": "<your current simplifier token>"
}
}
}
}
```
**Using Docker:**
```json
{
"mcpServers": {
"simplifier-docker": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--env",
"SIMPLIFIER_TOKEN",
"--env",
"SIMPLIFIER_BASE_URL",
"simplifierag/simplifier-mcp:latest"
],
"env": {
"SIMPLIFIER_BASE_URL": "https://<yourinstance>-dev.simplifier.cloud",
"SIMPLIFIER_TOKEN": "<your current simplifier token>"
}
}
}
}
```
### Troubleshooting
If the MCP fails to connect to Simplifier on startup, an error page will open in
your browser with details on the failure and information on how to fix the
problem.
TDQS
Scored across 17 tools
Tools are well-distinguished by resource type (Business Object, Connector, Data Type, etc.) and action (delete, update, test), with clear boundaries. Minor ambiguity exists between 'businessobject-update' and 'businessobject-function-update' as both involve updates, but their distinct targets (BO vs. BO function) are clarified in descriptions.
Naming follows a consistent pattern of 'resource-action' with hyphens (e.g., businessobject-delete, connector-call-test). All tools adhere to this snake_case-like convention, making them predictable and easy to parse. No mixing of styles or deviations observed.
17 tools is slightly high but reasonable for a comprehensive Simplifier management server covering multiple resource types (Business Objects, Connectors, Data Types, etc.). It provides full CRUD operations across these domains, though it could be streamlined by grouping similar actions.
The tool set offers complete coverage for managing Simplifier resources: CRUD operations for Business Objects, Connectors, Data Types, SAP Systems, and Login Methods, plus testing tools and logging. No obvious gaps exist; agents can perform full lifecycle management and debugging tasks.