Mcp Integration Suite

Overview

what is Mcp Integration Suite?

Mcp Integration Suite is a ModelContextProtocol (MCP) Server designed for SAP Integration Suite, facilitating the integration of various applications and services.

how to use Mcp Integration Suite?

To use the Mcp Integration Suite, clone the repository from GitHub, install the necessary dependencies, and configure your AI Clients MCP settings to include the integration suite.

key features of Mcp Integration Suite?

  • Supports cloud integration for seamless connectivity between cloud and on-premise applications.
  • API management capabilities for publishing and securing APIs.
  • Event mesh for handling business events across applications.
  • Integration advisor for B2B integration content specification.
  • Management of B2B relationships through trading partner management.
  • Access to over 150 non-SAP applications via open connectors.
  • Tools for package and integration flow management.

use cases of Mcp Integration Suite?

  1. Integrating various cloud services with on-premise applications.
  2. Managing APIs for secure and efficient data exchange.
  3. Automating business processes through event-driven architecture.
  4. Facilitating B2B integrations and managing trading partners.

FAQ from Mcp Integration Suite?

  • What are the system requirements for Mcp Integration Suite?

Node.js and NPM (Node Version > 20) are required to run the suite.

  • Can I use Mcp Integration Suite for all types of integrations?

Yes, it supports a wide range of integrations including cloud, on-premise, and B2B scenarios.

  • Is there documentation available for Mcp Integration Suite?

Yes, detailed documentation is provided within the repository and on the official SAP Integration Suite website.

Server Config

{
  "mcpServers": {
    "mcp-integration-suite": {
      "autoApprove": [],
      "disabled": false,
      "timeout": 300,
      "command": "node",
      "args": [
        "<proj path>/dist/index.js"
      ],
      "transportType": "stdio",
      "env": {
        "API_BASE_URL": "<API Base URL from BTP>/api/v1",
        "API_USER": "<SAP S User>",
        "API_PASS": "<S User Password>",
        "CPI_BASE_URL": "<CPI Endpoint URL (optional)>",
        "CPI_OAUTH_CLIENT_ID": "<CPI OAuth Data (optional) >",
        "CPI_OAUTH_CLIENT_SECRET": "<CPI OAuth Data (optional) >",
        "CPI_OAUTH_TOKEN_URL": "<BTP Auth URL>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
1nbuc
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago