onedevatlasBeta
Browse the atlas

Whose work the atlas stands on

The registries, documentation, directories and lists the atlas reads from or learned from. Each is credited by name and linked back, and where entries were first found through one, the count says how many.

Last changed

Where entries come from

  • npm registry
    216 artifacts

    The registry the CAP and UI5 packages are published to. Versions, licences, publishers and publish dates on every card are read from it nightly.

    Checked

  • GitHub API
    193 artifacts7 content items

    Stars, issue age, release cadence, last commit and contributors are read from its API nightly, and so is each maintainer's README, which the artifact page quotes.

    Checked

  • capireby SAP Cloud Application Programming ModelSAP Cloud Application Programming Modelorgmaintains 34 entriessap official
    14 artifacts

    CAP's official documentation, and the only source admitted for a claim about what the CAP core does. Its plugin page is the official list of CAP plugins.

    Checked

  • SAP Architecture Centerby SAPSAPorgmaintains 137 entries, wrote 14 docssap official
    9 content items

    Reference architectures with dated frontmatter, entered as readings attached to the capabilities they describe.

    Checked

  • SAP Community
    9 artifacts749 content items

    Blog posts under the CAP product tag are swept weekly with their title, author, date and board, and a post enters only once it is attached to what it explains.

    Checked

  • SAP Developer Centerby SAPSAPorgmaintains 137 entries, wrote 14 docssap official
    19 content items

    Tutorials, missions and groups, read from its public GraphQL endpoint and its build catalogue. Since mid-2026 it runs on an open platform with a knowledge graph of first-party learning content, which the atlas links into rather than repeats.

    Checked

  • SAP Help Portalby SAPSAPorgmaintains 137 entries, wrote 14 docssap official
    7 artifacts1 content item

    First-party documentation for what lies outside CAP, the ABAP platform above all.

    Checked

  • bestofcapjsby Marian ZeisMarian Zeispersonmaintains 35 entries, created 25 pieces, contributed to 86 entries
    1 artifact

    The CAP package directory, built from a curated list crawled against npm and GitHub. Its package names were an early seed for the atlas; its order was not taken.

    Checked

  • bestofui5by Marian ZeisMarian Zeispersonmaintains 35 entries, created 25 pieces, contributed to 86 entries
    9 artifacts

    The same engine for UI5, and the directory that keeps applications apart from packages, a split the atlas kept. Its package names seeded the UI5 door.

    Checked

  • awesome-capby Mauricio LaufferMauricio Laufferpersonmaintains 16 entries, created 4 pieces, contributed to 41 entriesindependent
    1 artifact

    A curated list of CAP links, strongest on tutorials, videos and books, which is where the package sources are thinnest.

    Checked

  • sap-ai-mcp-serversby Marian ZeisMarian Zeispersonmaintains 35 entries, created 25 pieces, contributed to 86 entries
    73 artifacts

    A generated catalogue of SAP MCP servers, agent skills and Claude plugins, each with its repository, licence and the date it was added, also published at sap-ai-tools.marianzeis.de. Names and repositories are taken from it; its sections are its own curation and stay there.

    Checked

  • SAP AI Skills Libraryby SAPSAPorgmaintains 137 entries, wrote 14 docssap official
    14 artifacts

    SAP's registry of AI skills and MCP servers, with a front end at skills.cloud.sap. It registers each skill and leaves the code in the publisher's repository, which is how the atlas treats skills as well.

    Checked

  • qmacro.org — DJ Adamsby DJ AdamsDJ Adamspersoncreated 22 pieces, contributed to 20 entriessap official

    A personal blog on CAP, the cds command line and the tools around them. Its index is swept weekly.

    Checked

  • Software-Heroesby XexerXexerpersonmaintains 7 entries, contributed to 8 entries
    5 artifacts12 content items

    A community ABAP, RAP, Fiori and BTP blog, and a set of standalone SAP developer tools, run by Xexer.

    Checked

  • SAP-samples/btp-service-metadataby SAPSAPorgmaintains 137 entries, wrote 14 docssap official
    18 artifacts

    SAP's machine-readable catalogue of BTP services: names, plans, deprecations and the data centres each plan is offered in. The BTP service entries are read from it.

    Checked

  • YouTube — SAP Developers playlistsby SAPSAPorgmaintains 137 entries, wrote 14 docssap official
    70 content items

    Its playlists are read as series: a playlist is a run of videos, and each video enters as a reading in its place.

    Checked

  • abaplint.app

    The abaplint figures on an ABAP repository's page are read nightly from abaplint.app's own record for it.

    Checked

Prior art

  • dotabapby Lars HvamLars Hvampersonmaintains 13 entries, wrote 1 doc, contributed to 92 entries

    The ABAP open-source list, admitting abapGit repositories against a published bar and running abaplint over each one for a cloud-readiness number. It computes a reading from the source itself, and its default order is not by stars.

    Checked

  • SAP Development Tech Radarby Tobias HofmannTobias Hofmannpersonmaintains 4 entries, contributed to 12 entries

    A community radar of SAP technology choices, placed through proposals that are discussed and voted on and published in dated six-month editions. The atlas took its governance and its dating from here, and for a time its rings, which were retired on 2026-09-06.

    Checked

  • ARC-1

    An ABAP MCP server over ADT, and where the atlas took its naming from: an organisation as the namespace, and SAP in the tagline, never in the name.

    In the atlas: arc-1arc-1mcp-serverAn MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abap
    Checked

A different layer

  • sap-devs CLIby SAPSAPorgmaintains 137 entries, wrote 14 docssap official

    A command line that puts SAP context packs into a coding agent, with a local MCP server of its own. The packs carry SAP's current core versions and known errors; the atlas carries what exists beside them.

    Checked

  • SAP's MCP servers

    Servers that let an agent act on a system: expose a CAP service as tools, generate and change a Fiori app. None of them says which option to choose, which is the question the atlas answers, and each is an entry here like any other option.

    In the atlas: @cap-js/mcp@cap-js/mcpcds-pluginA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, cap, @sap-ux/fiori-mcp-server@sap-ux/fiori-mcp-servermcp-serverSAP's Fiori MCP server, run as fiori-mcp, letting a coding assistant create and edit Fiori applications directly rather than describing the steps.sap official, ui5
    Checked

Other curated lists