Skip to content
SAP BAIP 90+ Services · 540+ Tools Claude · Cursor · ChatGPT

Give every AI agent full access to SSCV2

90+ SSCV2 services, 540+ AI tools, OData-style queries: all via Model Context Protocol. Works with Claude, Cursor, ChatGPT, and any MCP-compatible host.

Example Tool Call
// Example: Find a customer's latest cases
{
"tool": "cases_list",
"arguments": {
"search": "Muster AG",
"top": 10,
"orderby": "adminData.createdOn desc"
}
}
How It Works

From client to first query: in three steps

1
Step 1

Connect

We connect the server to your MCP client: locally via stdio (Claude Desktop, Cursor, Cline, Windsurf) or as a service operated by Spadoom on SAP BAIP.

2
Step 2

Authenticate

Point the server at your SSCV2 tenant with your own credentials. On BAIP, access is XSUAA-secured and isolated per subscription.

3
Step 3

Ask

Your AI agent calls 540+ tools with OData-style queries: list open cases, convert leads, update opportunities. Pagination and rate limits are handled automatically.

Features

Give AI agents full SSCV2 access

90+ SSCV2 Services

Full coverage: CRM, Service, Activities, Sales, Products, Surveys, Mashups, Visits, Identity (incl. SCIM), Extensibility, Workflow, ML/AI, and more.

540+ AI Tools

Standard CRUD plus specialized actions: lead conversion, case status changes, opportunity stage transitions, attachment uploads, extension field provisioning, UI customization.

OData-Style Queries

$filter, $top, $skip, $expand, $select, $orderby: query SSCV2 data naturally.

Automatic Pagination

paginate_all fetches up to 10,000 records, paginate_all_keyset up to 100,000 for larger datasets.

Rate Limit Handling

429 responses handled automatically with exponential backoff.

Operated on SAP BAIP

We run the server for you on SAP BAIP in the EU. Each user signs in with their own SAP login, so every change in the CRM carries their name, and every customer stays separate from the others.

API Coverage

The full SSCV2 API surface

Core CRM

Account, Contact, Individual Customer, Opportunity, Lead, Business Partner

Service

Case, Installed Base, Registered Product, Warranty, Functional Location, Service Level

Activities

Appointment, Task, Phone/Email/Chat/In-Person Interaction, Activity Plan, Visit

Sales

Sales Quote, Sales Territory, Campaign, Target Group, Survey, Survey Response

Products

Product, Product Group, Competitor, Competitor Product, Org Unit, Account Hierarchy

Extensions

Repository, Extension fields, UI customization, Custom services, Mashup, Page Layout, Alert, Notification, Workflow, ML/AI scenarios

Identity & Platform

IAM users, roles, tokens, OAuth2 configs, SCIM Users/Groups, Shell, Admin, I18N, CTI, Distribution Channels

Deployment Options

stdio for local AI clients (Claude Desktop, Cursor, Cline, Windsurf), StreamableHTTP for running on SAP BAIP, where several tenants run side by side and stay separate.

stdio

stdio

Drop-in for Claude Desktop, Cursor, Cline, Windsurf, and any MCP-compatible AI client. Point at your SSCV2 tenant: done.

StreamableHTTP

StreamableHTTP

Runs on SAP BAIP, operated by Spadoom. Sign-in runs through SAP, and the credentials of each customer stay separate.

FAQ

Frequently Asked Questions

What is the Model Context Protocol (MCP)?
An open standard that lets AI assistants call external tools and data sources in a controlled way: see modelcontextprotocol.io. Our server implements it for SAP Sales & Service Cloud V2.
Which AI clients work with the MCP Server?
Claude Desktop, Cursor, ChatGPT, Cline, Windsurf: any MCP-compatible host. Locally via stdio, or over StreamableHTTP for the managed service on SAP BAIP.
What do "90+ services and 540+ tools" cover?
The full SSCV2 API surface: accounts, contacts, opportunities, leads, cases, activities, products, surveys, workflow, extensibility, identity, and more. On top of CRUD there are specialized actions like lead conversion, case status changes, and attachment uploads: with OData-style queries ($filter, $expand, $top).
How can I use the MCP Server?
Two ways: Spadoom runs it for you on SAP BAIP, or we set it up locally for your team via stdio. Both connect to your own SSCV2 tenant. Pricing on request.
How is access secured?
The local stdio server runs in your environment with your own SSCV2 credentials. On SAP BAIP, sign-in runs through SAP (XSUAA): each user works with their own SAP login, and each customer's credentials stay separate.
Get started

Ready to put AI agents inside SSCV2?

Talk to us: we show you the server on your own SSCV2 tenant and set it up for your team, on SAP BAIP or locally.