MCP Server for SAP Cloud for Customer

Build 25.0.9440

Establishing a Connection

The CData MCP Server for SAP Cloud for Customer defines each connection to SAP Cloud for Customer as a named configuration that Claude can use when sending natural language queries.

You create and manage these configurations using the MCP Configuration Tool. The tool automatically handles formatting, storage, and registration with Claude Desktop.

Understanding Connection Configurations

Each connection configuration is stored in a .mcp file. This file includes the details needed to initialize the connector when Claude starts a session.

  • On Windows, configuration files are stored in "~/AppData/Roaming/CData/SAP Cloud for Customer Data Provider/".
  • On macOS, configuration files are stored in "~/Library/Application Support/CData/SAP Cloud for Customer Data Provider/".

The .mcp file is a text file that contains a list of connection properties and a timestamp. For example:

#Tue May 20 15:48:40 EDT 2025
AuthScheme=Basic
User=myUser
Password=myPassword
Security Token=myToken

The configuration tool handles these settings automatically. Each saved configuration enables Claude to launch a dedicated MCP Server instance with the correct connector and options. Manual file editing is not required.

Connecting to SAP Cloud for Customer

To identify your SAP Cloud for Customer instance, set the following:
  • Tenant: The full domain name of your SAP Cloud for Customer tenant.
  • URL: The URL corresponding to your SAP Cloud for Customer instance. You must specify this if it differs from the default service of "c4codata". Otherwise, omit this connection property.

Authenticating to SAP Cloud for Customer

User Credentials

Set the AuthScheme to Basic and specify the following:

  • User: Your SAP Cloud for Customer username.
  • Password: Your SAP Cloud for Customer password.

Azure AD

Set the AuthScheme to AzureAD.

Configuring a Custom Extension

This configuration requires a custom extension to SAP Hybris. This extension can be created using the yempty tool.

Connection Configuration

After configuring your custom extension, set the following to authenticate:

  • InitiateOAuth: GETANDREFRESH.
  • OAuthClientId: The application Id of the connector application, found in the Overview section of the app registration.
  • OAuthClientSecret: The client secret value of the connector application. Azure AD displays this when you create a new client secret.
  • CallbackURL: The redirect URI of the connector application. For example: https://localhost:33333
  • SSOProperties: Set the following additional properties, each separated by a commma, in the format A=B;C=D; etc.
    • Resource: The URL of your environment.
    • AzureTentant: The Id of the Azure AD tenant where the applications are registered.

Copyright (c) 2025 CData Software, Inc. - All rights reserved.
Build 25.0.9440