Alice V.
Entries
OData v2 only, and untouched since August 2025 — the same author's [Go port](artifact:oisee-odata-mcp-go) is where v4 support and the tool-explosion work went.
Python bridge generating MCP tools from OData v2 metadata
Universal mode trades discoverability for size: one generic tool is harder for a model to pick correctly than a named one, which is why it is not the default. On a small service, standard mode is the better answer.
Go binary bridging any OData v2 or v4 service to MCP
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Reach is the reason to use it and the reason to be careful: reading cluster tables and spool output goes well past what a development tool is normally pointed at. Decide what an agent may reach before granting it, not after.
ADT-to-MCP bridge in Go reaching past what ADT exposes
ABAP framework for chaining and orchestrating LLM calls
Vector database implemented in ABAP for document chunk retrieval
Transpiles ABAP to JavaScript to run on Node.js
Neither the package manifest nor the repository tree declares a licence.
MCP server turning a transport request into a WRICEF specification
Shim running an ABAP ICF handler behind an Express 4.x server
Core ABAP artifacts for code transpiled by @abaplint/transpiler
OData and Gateway shims serving SEGW-style services on Node.js
SAP GUI debugger script recording steps so execution can run backwards
Writing and topics
IN TOPICS
onedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.
Details
History
- vibing-steampunkThe policy is now a condition of Agent access to your code for ABAP, sourced to the policy itself.
- odata_mcpThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- odata_mcp_goThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- vibing-steampunkThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P3): the sentence each ABAP server carries and nobody had entered, which the tool role of the ABAP pilot reads as the arrow from the server to the system.
- vibing-steampunkPointed at the ADT nodes that entered the graph on 2026-09-15, from the project's own documentation.
- odata_mcpTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- odata_mcp_goTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- vibing-steampunkTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.
- First entry seenDiscovered via sap-ai-mcp-servers, GitHub API, Added by hand.
For your agent
- Ref
actor:oisee- JSON
- /actors/oisee.json
- MCP
- Connecting an agent