SAP MCP Server – lokale Variante
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Optional local server port. If changed, adjust the MCP client URL accordingly | 3000 |
| SAP_URL | Yes | SAP system URL, for example https://your-sap-host:44300 | |
| SAP_USER | Yes | SAP username with permissions for the required OData services | |
| SAP_CLIENT | Yes | SAP client/tenant, always three digits, for example 100 or 010 | |
| SAP_PASSWORD | Yes | SAP password. Quote it in .env, especially if it contains # or spaces | |
| NODE_EXTRA_CA_CERTS | No | Optional path to a local PEM file for additional enterprise certificates |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-sap-servicesC | Find SAP services by keyword/category. |
| discover-service-entitiesA | List all entities and their capabilities within a specific SAP service. Use this after finding a service to understand what data you can work with. |
| get-entity-schemaC | Get detailed schema information for a specific entity including properties, types, keys, and constraints. |
| execute-entity-operationA | Direct CRUD operations on SAP entities with precise OData queries. For natural language queries, use natural-query-builder first. Requires authentication. |
| check-sap-authenticationC | 🔐 Validate/associate authentication session. Call with session_id to authenticate. |
| sap-smart-queryC | Routes SAP requests to optimal tool |
| natural-query-builderC | Convert natural language to OData queries |
| smart-data-analysisC | Analyze SAP data patterns, trends, and generate actionable business insights with AI-powered statistical analysis. Provides automated data exploration and visualization recommendations. |
| query-performance-optimizerA | Optimize SAP OData query performance by analyzing execution patterns and suggesting improvements. Automatically identifies bottlenecks and recommends index strategies. |
| business-process-insightsC | Extract business process insights from SAP transactional data using AI pattern recognition. Identifies workflow inefficiencies and automation opportunities. |
| realtime-data-streamD | Stream SAP data via WebSocket |
| kpi-dashboard-builderD | Create and manage KPI dashboards |
| predictive-analytics-engineD | Run predictive analytics on SAP data |
| business-intelligence-insightsD | Generate business insights from SAP data |
| ui-form-generatorC | Creates dynamic forms for SAP entity operations with validation and SAP Fiori styling |
| ui-data-gridC | Creates interactive data grids with sorting, filtering, and export capabilities |
| ui-dashboard-composerC | Creates comprehensive KPI dashboards with charts and real-time data |
| ui-workflow-builderC | Creates visual workflow processes with step-by-step forms and approvals |
| ui-report-builderC | Creates comprehensive drill-down reports with analytical capabilities |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sap-services | List of all discovered SAP OData services |
TDQS
Scored across 19 tools
Several tools have near-identical purposes: smart-data-analysis, business-process-insights, business-intelligence-insights, and predictive-analytics-engine all claim to analyze SAP data and produce insights, and kpi-dashboard-builder overlaps heavily with ui-dashboard-composer (both create KPI dashboards). The query-routing tools (sap-smart-query, natural-query-builder, search-sap-services) also blur together, and the UI builders (ui-report-builder, ui-data-grid, ui-form-generator, ui-workflow-builder) are hard to distinguish without reading full descriptions.
Naming mixes verb_noun patterns (search-sap-services, get-entity-schema, execute-entity-operation) with noun-phrase tool names ending in -builder, -engine, -insights, and -stream (ui-report-builder, predictive-analytics-engine, business-intelligence-insights, realtime-data-stream). A few names even embed a different prefix convention (sap-smart-query) while others use natural-query-builder, so no single predictable pattern exists.
At 19 tools the set is heavy for a server whose real job is SAP OData discovery and CRUD, and much of that count comes from redundant analytics/insight and UI-building tools that duplicate each other's function. Trimming the overlapping insight and dashboard tools would leave a tighter, more usable surface.
The core OData lifecycle is reasonably covered (search services, discover entities, get schema, execute CRUD operations, plus authentication). However, gaps remain around batch/transaction operations, explicit session lifecycle/logout, and error or metadata diagnostics, while the analytics half of the surface is padded with overlapping tools rather than filling those gaps.