Overview

The Simplifier MCP (Model Context Protocol) Server connects AI assistants and tooling to a Simplifier low-code instance. It exposes operations to manage connectors, business objects, data types and to execute server-side logic or external system calls from an AI or other automation tooling. For platform administrators and integrators, the MCP server centralizes common integration tasks and simplifies building context-aware assistants that can read and act on a Simplifier environment.

This server is useful when you need programmatic control over Simplifier integration artifacts (connectors/logins), server-side JavaScript business objects, or the ability to invoke connector calls from an external agent without building a custom API layer. It supports core connector types commonly used in enterprise scenarios and can be run locally (npx) or inside Docker.

Repository: https://github.com/simplifier-ag/simplifier-mcp

Features

Manage Connectors and Logins: create, update, list connector configurations and credentials.
Manage Business Objects: create, update and execute server-side JavaScript BusinessObject functions.
Manage Data Types: create and inspect data structures used by connectors and business objects.
Execute Business Object Functions: run server-side JS functions with parameter passing and return values.
Execute Connector Calls: call external systems through configured Simplifier connectors (REST, SOAP, SQL, SAPRFC).
Platform browsing: list available connectors, business objects and system information for discovery.
Multiple run modes: run via npx (node) or Docker for easy integration into local AI agents.

Supported connector types:

Connector type	Typical use
REST	HTTP/JSON/REST endpoints
SOAP	SOAP/WSDL services
SQL	Direct database access via JDBC/SQL
SAPRFC	RFC calls to SAP backends

Installation / Configuration

Requirements:

Node.js (for npx mode) or Docker.
A running Simplifier instance and a valid Simplifier token.
Environment variables: SIMPLIFIER_BASE_URL, SIMPLIFIER_TOKEN

Run via npx (recommended for local development):

npx @simplifierag/simplifier-mcp@latest
# Example environment (Linux/macOS)
SIMPLIFIER_BASE_URL="https://<yourinstance>-dev.simplifier.cloud" \
SIMPLIFIER_TOKEN="<your-simplifier-token>" \
npx @simplifierag/simplifier-mcp@latest

Run via Docker:

docker run --rm -i \
  --env SIMPLIFIER_BASE_URL="https://<yourinstance>-dev.simplifier.cloud" \
  --env SIMPLIFIER_TOKEN="<your-simplifier-token>" \
  simplifierag/simplifier-mcp:latest

Example .mcp.json (for AI agent integrations that support MCP servers):

{
  "mcpServers": {
    "simplifier-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["@simplifierag/simplifier-mcp@latest"],
      "env": {
        "SIMPLIFIER_BASE_URL": "https://<yourinstance>-dev.simplifier.cloud",
        "SIMPLIFIER_TOKEN": "<your-simplifier-token>"
      }
    }
  }
}

If your Simplifier is on-premise, adjust SIMPLIFIER_BASE_URL accordingly.

Available Resources

Source and issues: https://github.com/simplifier-ag/simplifier-mcp
Simplifier community documentation and setup guide: https://community.simplifier.io/doc/current-release/extend/setup-mcp-to-interact-with-ai-models/
Supported resource types exposed by the MCP:
- Connectors (list, create, update, delete)
- Logins/credentials
- BusinessObjects (inspect, execute)
- DataTypes (view schemas)
- System info and discovery endpoints

Use Cases

Automate connector provisioning: create or update connector definitions for REST/SOAP/SQL/SAPRFC from a CI pipeline or admin assistant.
Run BusinessObject logic from an AI assistant: pass parameters to a server-side JS function to validate or enrich data, then receive structured results.
Fetch records via existing connectors: instruct an assistant to call an external REST API or database via a configured connector and return results to the user.
Integration testing: drive connector calls and business object executions from scripts or testing tools to validate integrations across environments.
Discovery and documentation: generate an inventory of connectors, business objects and data types for compliance or onboarding.

Example: execute a BusinessObject function (high level)

Use the MCP to list available BusinessObjects and pick the target.
Call the “execute” tool with the function name and JSON parameters.
MCP returns the function result (JSON or error), which an assistant can present or act upon.

Example: call an external REST API via a configured connector

Ensure a REST connector and login exist in Simplifier.
Use MCP to invoke the connector with method, path and parameters.
Receive parsed response data and forward to the agent or downstream process.

Troubleshooting and Notes

Tokens: Simplifier tokens change after re-login. If your token changes, restart the MCP process and update SIMPLIFIER_TOKEN. If integrated into an AI agent that registers MCP servers, you may need to remove and re-add the server configuration.
Startup connection failures: on failure to connect, the MCP opens an error page with diagnostic details—follow the instructions to fix base URL or token issues.
Security: do not store long-lived tokens in public repos. Use secure secret management for production deployments.

For detailed setup and advanced scenarios, consult the community docs linked above or open an issue in the GitHub repository.

Simplifier MCP Server: Manage Connectors and Business Objects