In a recent blog post, https://community.sap.com/t5/technology-blog-posts-by-members/odata-mcp-proxy-introduction/ba-p/14348684 , I introduced the OData MCP Proxy: a small server you deploy on BTP that turns any OData service into a fully‑featured MCP server using nothing but a configuration file. That proxy became the backbone of five BTP‑specific MCP servers I published on GitHub:
- ci-mcp-server — SAP Cloud Integration (github.com/lemaiwo/ci-mcp-server)
- ai-core-mcp-server — SAP AI Core (github.com/lemaiwo/ai-core-mcp-server)
- btp-mcp-server — BTP Core Services (github.com/lemaiwo/btp-mcp-server)
- btp-auditlog-mcp-server — BTP Audit Log (github.com/lemaiwo/btp-auditlog-mcp-server)
- btp-cf-mcp-server — Cloud Foundry V3 (github.com/lemaiwo/btp-cf-mcp-server)
That got me to a powerful but awkward place. Each MCP server lives on its own URL, has its own OAuth flow and exposes its own catalogue of tools. If a user wants to ask a natural‑language question that spans two or three of them, an MCP client has to juggle multiple connections and multiple logins. For a demo that is fine. For something I would hand to an operations colleague or a business user, it really isn’t.
Read More Technology Blog Posts by Members articles
#abap