btp-sap-odata-to

This MCP server exposes SAP OData services as dynamic MCP tools to enable natural language interactions with your ERP data. It implements a 3-level progressive discovery approach: Level 1 discover-sap-data provides lightweight service and entity lists, Level 2 get-entity-metadata returns full schemas for a selected entity, and Level 3 execute-sap-operation performs authenticated CRUD operations against the SAP OData services. Through this flow, you can ask questions like 'Show me top 10 banks' or 'Update bank with ID 1 to have street number 5', and the server translates your intent into appropriate MCP tools and OData calls. The built-in translation, parameter inference, and capability detection help ensure that your natural language requests map to valid OData operations with proper security and session handling.

Prerequisites:

• Node.js 18.x or higher
• Access to SAP S/4HANA or ECC with OData services enabled
• SAP BTP account with Destination and Connectivity services

Installation steps:

1. Install Node.js (if not already installed)
   • Download from https://nodejs.org/ or use a package manager
2. Install the MCP server package via npm (example using npx):
   • npm install -g lemaiwo-btp-sap-odata-to-mcp-server
3. Verify installation:
   • npx -y lemaiwo-btp-sap-odata-to-mcp-server --version
4. Configure environment variables as needed (see mcp_config.env example below) and start the server:
   • npx -y lemaiwo-btp-sap-odata-to-mcp-server

If you prefer a direct npm run approach, you can also install locally:

• npm install --save-dev lemaiwo-btp-sap-odata-to-mcp-server
• npx lemaiwo-btp-sap-odata-to-mcp-server

Note: Depending on your deployment model, you can also run via a package manager wrapper (npm/yarn) or use a containerized setup if provided by the package maintainers.

Tips and common issues:

• Ensure your SAP BTP Destination service and connectivity settings are correctly configured so the MCP server can reach your SAP OData endpoints.
• The 3-level discovery model helps minimize payloads; Level 1 returns lightweight data, while Level 2/3 fetch metadata and perform operations only as needed.
• Use the Level 1 tool discover-sap-data to identify available services and entities before requesting full metadata.
• Ensure proper authentication for CRUD operations (Level 3); authenticated operations may require XSUAA tokens or SAP-specific session handling.
• If you modify entity schemas or add new services, refresh metadata via Level 2 to ensure tools reflect current capabilities.
• Logs and error messages are designed to be user-friendly but may include technical details for debugging; enable MCP_DEBUG for verbose output during troubleshooting.