Today onedevatlas opens to everyone. It is one connected graph of what is built for SAP development, by SAP and by everyone else: packages, plugins, services, tools, MCP servers and skills, the problems they answer, the posts and talks that explain them, and the people who make them. One graph, read by people and by their agents.
Why it exists
Building has never been easier, and being found has never been harder. On 3 October the atlas listed 31 MCP servers for ABAP. Today it lists 42. Most of them are careful work, and many solve the same problem, because their makers could not see what was already there. Agents make it sharper: an agent knows what it was trained on and what the skills beside it describe, and the work of a freelancer, a partner or a customer team is rarely part of its answer.
The lists we have, for CAP, for UI5, for ABAP, are good and separate. What was missing is a view across the stacks, with SAP’s work and the community’s side by side, and a graph underneath that says how things relate.
A map drawn by capability
Every door, CAP, UI5, ABAP and BTP, and the smaller ones for SAP Commerce, SAP SuccessFactors and SAP Digital Manufacturing, has its own map. One hexagon is one capability, a concern a project has, and its colour says who is present: SAP, the community, both, or nobody yet. Open a tile and the capability page says what SAP ships, where that stops, and who else is present. Under a capability, use cases make the options comparable by the outcome they cover and the conditions under which they cover it, never by stars or downloads.
Behind the map is the graph itself, at /graph: select a node and its card says what it provides, who maintains it and what it depends on, each edge with one meaning.
The same answers for your agent
The hosted MCP server at https://onedevatlas.dev/mcp answers with the same facts the pages show. This exchange was recorded against the live server today: a question about letting a coding agent change ABAP in an on-premise system lands on a capability, then on an assessed use case with seven options, six covering it under conditions and one not known, and the four things that decide between them for your system.
Explore, and TechEd week
The third way in is a flight. Explore and Play is the same graph as a place: make an orb, design a ship and fly through the ecosystems. Until Sunday 1 November, midnight in Berlin, it is shared: sign in with GitHub, meet other pilots, play rock, paper, scissors (SAP style) and collect points for what you look at. Then the boards freeze, and the leaders stay in the atlas’s history.
Take part
If your work is missing or something about it is wrong, open an issue. Anything about a person goes directly through the contact form. Maintainers can sign in and write a note on their own entry.
The full article explains the words the atlas uses and how to read a capability page, and its discussion is open.
See you at TechEd, or in flight. 🚀
#abap