Agentic AI Interoperability in SAP: MCP, A2A, Agent Gateway and the SAP API Policy

Keep this: job aid

Agent interoperability on SAP: design review card

• Job first: read data → MCP tool; delegate a task → A2A; deterministic bulk → integration flow, not an agent.
• API Policy 2.2.2: an AI that plans or sequences SAP API calls, or bulk extraction, needs an SAP-endorsed pathway.
• Endorsed routes: MCP Gateway in SAP Integration Suite; A2A via Agent Gateway (not GA as of Oct 2026); zero-copy data services.
• Published APIs only (section 1.2); ODP-RFC is unpermitted for third-party egress.
• MCP Gateway sources: API artifact, OpenAPI endpoint, RFC back end, remote MCP server (Streamable HTTP). Plan-dependent: SAP Note 2903776.
• Identity: user-delegated tokens or RFC 8693 exchange to a scoped token; never a shared broad user.
• Tools: few, narrow, read-only first; writes as drafts behind existing approvals ($10,000 PR release, $25,000 PO approval at Contoso).
• Log every call: user, agent, tool, redacted parameters, target API, status, latency.
• Test prompt injection through documents and tool responses on every release.
• Label each component GA / plan-dependent / roadmap / announced, with a source and re-verify date.