Person

Oleksii Kyslytsia

GitHub@fr0sterlast push

Capabilities1

Provides 1
Agent access to your codeABAPAgent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.

Entries2

Group by
EntrySignals
Maintains2
@mcp-abap-adt/corev20.1.0
Functional boundary

ABAP ADT MCP server published as an npm scope and plugin

fr0ster/mcp-abap-adt
Functional boundary

ABAP MCP server with full CRUD on on-premise and ABAP Cloud

Writing and topics1

IN TOPICS

The atlas is now in betaTopic, edition 1names fr0ster/mcp-abap-adt

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

History7
  • fr0ster/mcp-abap-adtconnects → the ABAP platform and the BTP ABAP environment, through ADT, from the README's first sentence and its list of the systems it works withThe 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.
  • fr0ster/mcp-abap-adtdescription, provides[0].what_it_does, flavors, identity.license → legacy systems not supported at present; Apache-2.0 for the repository and the library, AGPL-3.0-only for the standalone serverThe README read on 2026-09-27 says legacy support is parked on a branch until it can be tried against a live system, and its licence table names two licences by package; the entry's sentences rested on the earlier README, and the comparison with other entries was the entry's own and is gone.
  • fr0ster/mcp-abap-adtlineage → inspired by mario-andreschak/mcp-abap-adtThe README's acknowledgment names the project it started from; the graph holds it, and the edge is the maintainer's own sentence.
  • fr0ster/mcp-abap-adtdescription.one_line, description.what_it_solves, provides[0].what_it_does → corrected against the READMECorrected against the README: SAP_AUTH_TYPE takes basic, JWT/XSUAA, service key, certificate and kerberos; RFC is a connection type, not an authentication method. 'Four' matched neither count.
  • @mcp-abap-adt/coreentry → createdTriaged 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.
  • fr0ster/mcp-abap-adtentry → createdTriaged 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.
For your agent