AI Core MCP Server
Exposes SAP AI Core APIs as MCP tools, enabling AI assistants to manage AI Core lifecycle and administration through natural language.
README
AI Core MCP Server
An MCP (Model Context Protocol) server for SAP AI Core, powered by odata-mcp-proxy. It exposes SAP AI Core APIs as MCP tools, allowing AI assistants like Claude to manage your AI Core landscape through natural language.
The entire server is defined through a single JSON config file -- no custom code required.
How It Works
This project uses the odata-mcp-proxy npm package, which maps OData/REST services to MCP tools based on a configuration file. You provide a config describing your APIs and entity sets, and the proxy generates the corresponding MCP tools automatically.
AI Assistant (Claude, Cursor, etc.)
|
| MCP Protocol (HTTP or stdio)
v
odata-mcp-proxy
|
| REST + OAuth2 (via BTP Destination Service)
v
SAP AI Core APIs
Think of it like the SAP Application Router -- a ready-made runtime you configure, not code you write.
Exposed AI Core APIs
The config file (ai-core-api-config.json) defines two API groups:
Lifecycle Management (/v2/lm)
| Tool | Operations | Description |
|---|---|---|
Scenarios |
list, get | AI scenarios -- logical groupings of executables that define a ML use case |
ScenarioVersions |
list | Versions of a scenario |
Executables |
list, get | Workflow templates (training) and serving templates (inference) under a scenario |
Models |
list | Models available in a scenario (e.g. LLMs in the generative AI hub) |
Configurations |
list, get, create | Parameter sets binding a scenario/executable to inputs and hyperparameters |
Executions |
list, get, create, update, delete | Training or batch inference runs, tracked through lifecycle states |
Deployments |
list, get, create, update, delete | Running model-serving instances providing real-time inference endpoints |
Artifacts |
list, get, create | Registered references to datasets, models, or files in an object store |
ExecutionSchedules |
list, get, create, update, delete | Cron-based schedules that automatically create executions |
Metrics |
list, delete | Training and evaluation metrics recorded during executions |
Meta |
list | Runtime capabilities, supported features, and API version info |
DatasetFiles |
get, create, delete | Upload, download, and delete files in the object store |
Administration (/v2/admin)
| Tool | Operations | Description |
|---|---|---|
Repositories |
list, get, create, update, delete | Onboarded git repos containing workflow/serving templates |
Applications |
list, get, create, update, delete | ArgoCD applications that sync git repo content into AI Core |
DockerRegistrySecrets |
list, create, update, delete | Credentials for pulling private container images |
ObjectStoreSecrets |
list, create, update, delete | Credentials for S3, Azure Blob, GCS, or other object stores |
GenericSecrets |
list, get, create, update, delete | Key-value secrets (API keys, tokens) for executions and deployments |
ResourceGroups |
list, get, create, update, delete | Tenant isolation units that segregate AI assets and workloads |
Services |
list, get | Service broker registrations exposing AI Core capabilities |
Prerequisites
- Node.js 18+ (20+ recommended)
- SAP BTP account with SAP AI Core provisioned
- BTP Destination configured for the AI Core API (
AI_CORE) with OAuth2 authentication - Cloud Foundry CLI (
cf) and MBT Build Tool (mbt) for deployment
Project Structure
ai-core-mcp-server/
├── package.json # Start script + odata-mcp-proxy dependency
├── ai-core-api-config.json # API configuration (defines all MCP tools)
├── mta.yaml # BTP Cloud Foundry deployment descriptor
├── xs-security.json # XSUAA OAuth2 configuration
├── default-env.json # Local dev credentials (gitignored)
└── LICENSE
Getting Started
1. Install dependencies
npm install
2. Configure BTP destination
Create a BTP Destination pointing to the AI Core API:
| Destination | URL |
|---|---|
AI_CORE |
https://api.ai.prod.<region>.aws.ml.hana.ondemand.com |
The destination should use OAuth2 client credentials authentication with the AI Core service key.
3. Local development
Create a default-env.json with your BTP service bindings (XSUAA, Destination, Connectivity) to run locally:
npm start
This runs odata-mcp-proxy --config ai-core-api-config.json.
4. Deploy to BTP
npm run build:btp # Build MTA archive
npm run deploy:btp # Deploy to Cloud Foundry
The MTA deployment provisions three service instances:
- Destination (lite) -- resolves API endpoints and manages OAuth2 tokens
- Connectivity (lite) -- enables secure backend connectivity
- XSUAA (application) -- handles OAuth2 authentication with role-based access control
Security
The XSUAA configuration (xs-security.json) defines three role templates:
| Role | Scopes | Description |
|---|---|---|
MCPViewer |
read | Read-only access |
MCPEditor |
read, write | Read and write access |
MCPAdmin |
read, write, admin | Full administrative access |
OAuth2 redirect URIs are pre-configured for Claude.ai, Cursor, Microsoft Teams, and local development.
Creating Your Own MCP Server
This project demonstrates how easy it is to create a custom MCP server using odata-mcp-proxy. To build your own:
-
Create a new project and install the dependency:
mkdir my-mcp-server && cd my-mcp-server npm init -y npm install odata-mcp-proxy -
Add a start script to
package.json:{ "scripts": { "start": "odata-mcp-proxy --config my-api-config.json" } } -
Define your APIs in a config file (
my-api-config.json):{ "server": { "name": "my-mcp-server", "version": "1.0.0", "description": "My custom MCP server" }, "apis": [ { "name": "my-api", "destination": "MY_BTP_DESTINATION", "pathPrefix": "/api/v1", "csrfProtected": true, "entitySets": [ { "entitySet": "Products", "description": "Product catalog", "category": "master-data", "keys": [{ "name": "Id", "type": "string" }], "operations": { "list": true, "get": true, "create": false, "update": false, "delete": false } } ] } ] } -
Add your
mta.yaml,xs-security.json, and BTP Destinations, then deploy. That's it -- no code to write.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。