Hosting

SAP Automation Pilot tenant-hosted remote MCP

Transport

Streamable HTTP

Endpoint

Local process; no hosted endpoint documented

Authentication

Uses the authentication configured for the SAP BTP tenant and its Automation Pilot MCP server; consult the tenant-generated client configuration.

Requirements

• SAP BTP tenant with SAP Automation Pilot and MCP feature access.
• Permission to create/manage Automation Pilot MCP servers and commands.

Setup steps

1. In SAP Automation Pilot, open MCP Servers and create a server.
2. Choose the commands to expose as MCP tools and save/activate the server.
3. Copy the tenant-generated endpoint and client configuration from the server details.
4. Configure an MCP client with those exact tenant values and authenticate using the tenant-supported method.
5. Inspect tools/list before use; exposed commands can trigger operational workflows.

Each server has a tenant-defined command roster (up to 50 configured tools) plus the automatic get_execution tool.

• get_execution

  Poll a command execution for status, progress, output, and errors.

  01

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Requires tenant-level SAP Automation Pilot access and explicit command configuration.
• Plan limits on number of exposed tools vary; the vendor documentation describes different limits by plan.
• Connection and functionality were not tested in this research pass.

• official vendor server management

  SAP documents creating and managing tenant MCP servers and selecting command tools.

• official documentation

  Current publisher or maintainer documentation reviewed 2026-10-28T19:00:00.000Z.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.