Enterprises are increasingly embracing artificial intelligence, embedding tools like Claude, Microsoft Copilot, and ChatGPT into daily routines. Across corporate environments, workers rely on these generative AI models for everything from generating content to complex reporting and data analysis. However, when users inevitably ask whether their preferred AI tool can interact directly with critical enterprise systems like SAP, the answer has traditionally fallen short. Organizations frequently encounter roadblocks, often told that the integration is either nonexistent or severely limited.
Compounding these technological hurdles are evolving corporate policies. SAP’s updated API policy mandates that customer AI access to SAP-published APIs must go through endorsed, standardized pathways. Consequently, establishing a functional connection between a third-party AI assistant and an SAP Enterprise Resource Planning (ERP) system has become an intricate engineering task. Worse still, this custom integration work often needs to be repeated from scratch every time an organization adopts a new AI platform. As enterprises rapidly diversify their AI stacks, this technical debt accumulates far faster than internal IT teams can address it.
To solve this persistent industry challenge, Precisely has announced the launch of the new Precisely Automate MCP Server alongside native OData support in Precisely Automate. Together, these two capabilities provide any Model Context Protocol (MCP)-compatible AI assistant with governed, standards-based access to SAP automation workflows. This innovation allows enterprises to connect AI agents to core SAP processes without having to rebuild the underlying integration every time their preferred AI tools or underlying infrastructure change.
The Growing Complexities of Manual AI-to-SAP Connectivity
When a finance lead wants an AI assistant to trigger a journal entry workflow, or a supply chain manager requires an update to a vendor record, building a bridge between the AI tool and SAP is no small feat. It demands custom API development, meticulous authentication configurations, and ongoing maintenance. When the enterprise inevitably introduces another AI platform to handle specialized tasks, the entire integration cycle must start over.

Most modern enterprises are not converging on a single, monolithic AI tool. Instead, they operate multiple systems in parallel, utilizing Copilot for productivity tasks, Claude for deep data analysis, ChatGPT for specific operational workflows, and SAP’s native Joule for dedicated enterprise tasks. Each of these applications represents a separate integration project if it needs to connect to core SAP instances. For IT departments already stretched thin by complex S/4HANA migration projects, this integration backlog represents an untenable operational burden.
The stakes have grown even higher due to SAP’s evolving connectivity policies regarding third-party software and large language models (LLMs). Organizations that rely on legacy scripting approaches, such as BAPI, RFC, and traditional GUI automation, are discovering that these methods face mounting restrictions within cloud environments, particularly in S/4HANA Cloud and RISE with SAP deployments. The overarching trajectory from SAP is unequivocal: enterprise integrations must run through sanctioned, API-based protocols. What was once considered a best practice is rapidly hardening into a strict compliance requirement.
Research conducted by Precisely and ASUG highlights the widespread pressure organizations face as they attempt to modernize their enterprise architectures. Businesses capable of connecting artificial intelligence to SAP through a unified, standards-based interface will secure a distinct competitive advantage over competitors still struggling to manage fragmented, point-to-point integrations.
Inside the Precisely Automate MCP Server
The Precisely Automate MCP Server is engineered around the Model Context Protocol, an open standard originally developed by Anthropic and rapidly embraced across the broader artificial intelligence ecosystem. By leveraging this framework, the server exposes Automate Studio scripts and Automate Evolve workflows as AI-callable tools. Consequently, virtually any MCP-compatible AI client can discover and invoke these pre-configured processes through a single, unified configuration layer.

Interactions occur naturally in plain language, eliminating the need for routine IT support tickets or prolonged waits for developer resources. While Automate Studio and Evolve handle the underlying SAP interactions in the background, governance controls remain strictly intact.
It is important to note that the underlying Studio scripts and Evolve workflows exposed by the MCP Server must still be built and configured initially. This is not a zero-configuration shortcut to cloud SAP automation. Rather, its primary value lies in eliminating the recurring overhead of re-exposing those established workflows to every newly adopted AI platform. Enterprises can build their automation logic once and connect it securely to any MCP-compatible AI tool moving forward.
Leading AI platforms including Claude, ChatGPT, Microsoft Copilot, Joule, and Gemini are already compatible with the standard. As additional platforms adopt the protocol, they will be able to plug directly into the Automate MCP Server without requiring additional custom integration work. This architecture compounds the long-term value of every automation script built within Studio or Evolve, shifting the paradigm so that new AI tools no longer trigger costly, redundant integration projects.
This release represents a key component of a broader corporate strategy at Precisely. The company is currently rolling out enterprise MCP Server support across multiple solutions within its software portfolio, effectively connecting autonomous AI agents to data quality, location intelligence, master data management, and workflow automation capabilities through a unified interface.

The Critical Need for Native OData Support in Cloud SAP Automation
SAP has methodically shifted its connectivity policies toward open standards, and recent updates have only accelerated that trajectory. Direct Business Application Programming Interface (BAPI) calls, Remote Function Call (RFC) scripting, and graphical user interface automation face increasing restrictions or outright lack of support for third-party software and LLMs operating within SAP cloud environments. Organizations banking their cloud automation strategies entirely on legacy methods face significant operational risks.
Open Data Protocol, commonly known as OData, serves as SAP’s preferred REST-based API standard for modern integrations. It is the required methodology for Clean Core environments, including RISE with SAP and S/4HANA Cloud, and represents the officially endorsed approach for all new third-party software connectivity. By embedding native OData support directly into Automate Studio, Precisely ensures that AI-driven SAP automations operate via SAP-sanctioned protocols from day one.
The functional scope accessible through OData is vast. The SAP Business Accelerator Hub currently publishes more than 2,700 OData APIs spanning SAP’s entire cloud application portfolio. This comprehensive coverage includes S/4HANA Finance, SAP SuccessFactors, SAP Ariba, SAP Concur, and SAP Customer Experience, among others. This breadth ensures that Automate-driven cloud workflows can extend seamlessly across the entire enterprise application landscape rather than remaining siloed within legacy on-premises processes.
In practical terms, native OData support enables organizations to comply with Clean Core mandates while embracing modern automation paradigms. Historically, maintaining compliance with SAP architecture guidelines while empowering flexible AI integration presented competing engineering requirements. The latest platform updates bridge this divide, making both objectives achievable within a single framework.

Implications for Enterprises Building Toward AI-Ready Data
For autonomous systems to deliver genuine value inside an enterprise SAP environment, they require reliable, strictly governed access to core data assets, including financial ledgers, supply chain operations, human resources records, and procurement pipelines. Without secure access, artificial intelligence tools are forced to operate in isolation around SAP rather than integrating productively within it.
AI systems must possess the capability to both read from and write back to authoritative systems of record. The Automate MCP Server extends this operational reach directly into SAP, allowing authorized AI agents to trigger validated SAP workflows while ensuring every action remains logged and fully traceable.
For organizations already utilizing Automate Studio or Evolve, this release transforms existing automation investments into immediate AI-native assets. Established scripts, complex workflows, and internal governance configurations become accessible to the everyday productivity tools employees rely on, without requiring a disruptive re-platforming effort.
Meanwhile, enterprises approaching cloud SAP automation for the first time through an AI-first lens will find that the Automate MCP Server provides a flexible foundation that avoids vendor lock-in with a single AI provider. Recent collaborative research by Precisely and ASUG revealed that 75 percent of SAP-focused organizations view low-code and no-code capabilities as critical factors when selecting an automation platform. Governing complex SAP processes through natural language represents the natural evolution of this trend, and the necessary underlying connectivity layer is now fully available to the market.