MCP Gateway in SAP Integration Suite: Exposing APIs and Integration Flows as Governed Tools for AI Agents

Keep this: job aid

MCP server release checklist

• Every tool maps to a Published API; the API Policy version reviewed is recorded with the date.
• Feature status checked in What's New (GA date) and SAP Notes 2903776 (plan) and 3769634 (region).
• Tools are task-shaped, at most a handful per job; schemas trimmed with tool simplification; descriptions written for a model.
• Reads and writes live in separate MCP servers; write tools run as the end user with normal approvals.
• Authentication is OAuth and first; Authorization checks a scope only intended users hold.
• Quota, Surge Protection and IP Filter values are set and justified; payload limits sit on the source API artifact.
• Interactive agents use IdP user tokens with principal propagation; technical users only for narrow background jobs.
• Credentials come from a Developer Hub subscription for the agent, never from shared service keys or chats.
• Tests cover discovery, schema, 401/403/429, model behavior on real questions, and synchronization regression.
• Production runs at log level Info; Trace only short and approved; the audit trail can be rebuilt for a sample call.