get-partner-metadataLABSCO SUMMARY
Splitting partner management out is right — it is a different domain with a different toolchain.
The main server is Node; this one is Java, because that is what the underlying content needs. Keeping them separate means neither drags the other's runtime along, and you install only the half you need. Trading partner agreements are also the part of B2B integration that is genuinely fiddly to inspect by hand, which makes it a sensible thing to be able to ask about. Same experimental caveat as its sibling.
What it is
A companion server covering Trading Partner Management in SAP Integration Suite — the agreements and partner profiles that B2B exchange runs on. Also labelled experimental.
What you get
Access to trading partner management content, which the author's main Integration Suite server does not cover.
Requirements
Java and Gradle; built from source. The author recommends running it beside their Integration Suite server.
Setup effort
Build from source — git clone https://github.com/1nbuc/mcp-is-tpm.git
USE CASES
Inspecting a partner agreement
Ask rather than clicking through the console.
Running the pair
Alongside the Integration Suite server, as the author intends.
49 tools
Listed in project docs. Your client may show a different list.
get-partnercreate-trading-partnerget-systems-of-partnercreate-systemget-system-typescreate-identifierget-qualifiers-codelistcreate-communicationget-sender-adaptersget-receiver-adapterscreate-signature-verify-configactivate-signature-verify-configget-all-company-profile-metadataget-all-agreement-metadataget-all-agreement-template-metadataget-agreement-templatecreate-agreement-with-bound-templateget-agreement-b2b-scenarioupdate-b2b-scenariotrigger-agreement-activate-or-update-deploymentget-all-mig-latest-metadataget-mig-raw-by-idget-mig-nodes-xpathget-all-mig-fieldsget-mig-documentation-entryget-mig-proposalapply-mig-proposalcreate-mig-draft-all-segments-selectedcreate-migchange-mig-field-selectionget-all-mags-metadatacreate-mapping-guidelinestest-mag-with-messagesearch-interchangesget-interchange-payloadsdownload-interchange-payloadget-interchange-last-errorget-type-systemsget-type-system-messagesget-type-system-message-fullcreate-custom-messageget-type-system-identifier-schemesget-all-business-process-rolesget-all-business-processesget-all-industry-classificationsget-all-product-classificationsget-all-productsget-all-contries-or-regionsBEFORE YOU INSTALL
What to know first
Tools you get
49 tools named in the project's documentation.
Requires
- Java and Gradle
- CPI_URL in your environment
- CPI_USER in your environment
- CPI_PASSWORD in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/1nbuc/mcp-is-tpm.git
cd mcp-is-tpm
./gradlew buildAdd the mcpServers block below to your AI client's MCP config, filling in the paths and CPI_* values
MCP Clients
Any MCP client
{
"mcpServers": {
"mcp-is-tpm": {
"command": "java",
"args": [
"-Dlogging.pattern.console=",
"-Dspring.main.web-application-type=none",
"-Dspring.ai.mcp.server.stdio=true",
"-jar",
"<YOUR_PROJECT_PATH_MCP_TPM>/app/build/libs/app-0.0.1-SNAPSHOT.jar"
],
"autoApprove": [],
"env": {
"CPI_URL": "https://<YOUR_SUBDOMAIN>.cpi.url.hana.ondemand.com",
"CPI_USER": "S001234567",
"CPI_PASSWORD": "myPass123",
"CPI_UNIVERSAL_MAIL": "mail@company.de"
}
}
}
}