In my previous blog post I showed how the odata-mcp-proxy can turn an HTML page into an interactive MCP tool: https://community.sap.com/t5/technology-blog-posts-by-members/odata-mcp-proxy-interactive-ui-views-in-your-mcp-server/ba-p/14469713
That post was about what comes out of the MCP server. This one is about what goes in: how does the model know which tool to call, what payload to send and how to keep the responses small?
What if the MCP server would only take care of the connection to the data source and something else would explain to the model how that server should be used? That something else exists, it is called a skill. A skill is a markdown file with instructions that the AI client loads when it needs it. The MCP server owns the connection, the skill owns the knowledge. Two different things, two different owners, two different places.
In this blog post, I’ll walk you through how I combined a skill with my BTP MCP server, why this split improves performance, reduces token consumption and applies a kind of segregation of duty between the connection and the know-how. The full example is the btp-mcp-server project on GitHub: https://github.com/lemaiwo/btp-mcp-server
Read More Technology Blog Posts by Members articles
#abap