Evolve MCP Server - Automate_Evolve - Latest

Automate Evolve User Guide

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Automate > Automate Evolve
Version
Latest
ft:locale
en-US
Product name
Automate Evolve
ft:title
Automate Evolve User Guide
Copyright
2026
First publish date
2018
ft:lastEdition
2026-10-13
ft:lastPublication
2026-10-13T12:25:18.315000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Automate
L4_Investment_Segment
SAP Automation
L5_Product_Group
Winshuttle Enterprise
L6_Product_Name
Automate Studio
Automate Studio Manager
Automate Evolve
Table 1. Changes in this topic
Change type Description
Introduced in version 26.1 Added support for the Automate Evolve MCP Server, enabling AI assistants to access and manage Automate Studio scripts, SAP OData APIs, Evolve tasks, processes, and documents through the Model Context Protocol (MCP).

Model Context Protocol (MCP) is an open protocol that standardizes how AI assistants connect to external tools and data sources. The Automate Evolve MCP Server implements this protocol, exposing comprehensive Automate Evolve functionality as MCP tools. This includes SAP integrations, workflow management, document operations, and task processing. Any MCP-compatible AI assistant can interact with Automate Evolve through natural language, enabling seamless automation and data access without requiring users to navigate the Automate Evolve interface directly.


MCP host MCP client 1 MCP client 2 MCP client 3 Host applications Claude · Gemini GitHub Copilot Microsoft 365 JSON-RPC Streamable HTTP JSON-RPC Streamable HTTP JSON-RPC STDIO MCP server 1 · remote Tool 1 Tool 2 MCP server 2 · remote Tool 1 MCP server 3 · local Tool 1 SQL DB Snowflake SAP X / social Host & clients Remote server Local server Data / infra

For MCP Server installation steps, see the Automate Evolve Installation guide.

Key components

The MCP architecture consists of the following components:

MCP Host

An AI-powered application that embeds an MCP client and coordinates user interactions, conversations, and tool execution. Examples include Claude for Desktop and Microsoft Copilot Studio.

MCP Client
A component embedded in the MCP host that establishes and manages the communication with MCP server. The MCP client sends requests to MCP server and receives the response via MCP protocol.
MCP Server
An MCP-compliant service that exposes tools and resources to MCP clients over the MCP protocol. The Automate Evolve MCP Server connects to the Evolve Server and exposes its capabilities as MCP tools.
MCP Tools
Tools exposed by an MCP server that an MCP client can invoke. Tools accept parameters and return results.
Transport
The communication layer between the MCP client and the MCP server. JSON-RPC messages use one of two transport mechanisms to travel between the MCP client and server. The Automate Evolve MCP Server falls under the Streamable HTTP category.
  • Streamable HTTP: Used for remote MCP servers. Automate Evolve uses Streamable HTTP. This mechanism sends data in small chunks over a continuous channel.
  • STDIO: Used for local MCP servers running on the same machine as the MCP client.
Server-Sent Events (SSE) was a previous transport mechanism and is deprecated. Streamable HTTP replaced it.
JSON-RPC
The message format used for communication between the MCP client and the MCP server. JSON-RPC is a JSON-based format encoded with UTF-8 that is used for executing remote procedures (functions). All MCP tool requests and responses travel as JSON-RPC messages over the configured transport.

MCP and Evolve

The Automate Evolve MCP Server exposes tools covering the following categories. Some tools are dynamically created by a user in Automate Evolve, while others are part of the Automate Evolve installation.

  1. Invoke Studio Scripts: Studio Scripts available in a Automate Evolve document library of type SAPAPIStore can be invoked over the MCP protocol. This covers all Studio Scripts except those for which the Upload type Bulk is selected in Studio Mapper. These are dynamically created tools.
  2. Invoke SAP OData APIs: SAP OData endpoints can be invoked directly through Automate Evolve without creating any Studio Script. GET operations are available by default. Write operations are disabled by default. These are dynamically created tools.
  3. Manage Tasks, Processes, and Documents: Task, process, and document management includes starting a Form Workflow process, viewing tasks, completing tasks, reassigning tasks, viewing processes, completing processes, and viewing documents. The tool to start a Form Workflow process is a dynamic tool and the remaining tools are part of the Automate Evolve installation.

For dynamic tools, options are available in Automate Evolve to assemble the corresponding tool. After assembling a new tool, re-assembling an existing tool, enabling a tool, or updating a tool description, the MCP client must be restarted because MCP clients load tools only on launch and do not refresh automatically. Automate Evolve rejects tool execution if the tool is disabled, without requiring the MCP client to be restarted.


MCP host MCP client 1 MCP client 2 MCP client 3 Host applications Claude · Gemini GitHub Copilot Microsoft 365 JSON-RPC Streamable HTTP Evolve MCP server Remote Tool 1 Invoke Studio scripts Tool 2 Invoke SAP OData Tool 3 Control tasks/processes Studio scripts T Q SAP Workflow engine Host & clients Evolve MCP server External systems

The Automate Evolve MCP Server is a separate website built on modern .NET. The existing Automate Evolve website is based on .NET Framework 4.8, which does not support hosting an MCP server. The MCP Server website communicates with the Automate Evolve website over REST-based endpoints. Protocol-level handling is performed by the MCP Server website, while functional aspects of MCP tools are handled by the existing Automate Evolve website. The MCP Server website can be installed on the same server as Automate Evolve or on a separate server.


MCP Client MCP Protocol Implementation Business Layer of MCP Tools Authentication Info HTTP Streamable Authentication Info REST API Evolve MCP Server Website Standard Evolve Website (.NET Framework 4.8) Automate Evolve Internal

Available MCP tools

When an MCP client connects to the Automate Evolve MCP Server, the tools configured for the site are visible to the MCP client. Two tool categories require assembly before they are available, the remaining tools are part of the Automate Evolve installation. For full descriptions and filtering options, see MCP Server tool types.

Tool Description
Studio script tools Invoke Automate Studio scripts (RFC, Fiori, GUI HTML). Assembled per script from a library of type SAPAPIStore. Requires assembling of Tool from user. Script with Bulk Type as Upload cannot be assembled as Tool.
SAP OData API tools Invoke SAP OData APIs on a Fiori server. Assembled per SAP server. GET operations only by default. Requires tool assembly by the user at the App level.
GetAssignments Fetches task assignments for the user in whose context the MCP client is running. An Admin user can fetch assignments of all users by explicitly mentioning in prompt.
GetProcesses Fetches running processes accessible to the user in whose context the MCP client is running.
GetDocuments Fetches Documents of the user. User can ask to fetch details of a particular document which would return Form fields, version history and process history.
CompleteAssignment Approves, rejects, save or completes an assignment with optional form field updates.
TaskReassignment Reassigns an existing task to a different user. Admin user can reassign the task.
CompleteProcess Allows an administrator to approve, reject, or cancel a process with a note, thereby completing the process.
Start Form Process Starts a new form-based process for a specific form solution. Requires assembly per solution.

Configuration parameters

The following parameters can be used when configuring an MCP client to connect to the Automate Evolve MCP Server:

Parameter Description
MCP Server URL The URL of the Automate Evolve MCP Server. Used in MCP client configuration to connect to the MCP Server.
MCP Server key (evolve-mcp-key) The authentication key for the MCP Server. Used in MCP client configuration as the value for the evolve-mcp-key header. If not provided, the MCP Server uses OAuth authentication.

MCP Server authentication

The Automate Evolve MCP Server supports two authentication methods: OAuth 2.1 and API key (evolve-mcp-key). Both methods run every tool call under a specific user context that determines the SAP credentials, Evolve roles, and access rights used during execution.

OAuth 2.1 (Authorization Code flow with mandatory PKCE)

MCP clients can authenticate using OAuth 2.1 with Dynamic Client Registration when the MCP Server is configured for OAuth authentication, regardless of whether Automate Evolve uses Windows, SAML, or OAuth authentication. The MCP client initiates the Authorization Code flow, which triggers the existing Automate Evolve login behavior through a web browser. A bearer token is generated in the context of the user who successfully logs in. No separate identity store is required. OAuth requires the Automate Evolve website to be served over HTTPS, it is not supported over HTTP.

Note: OAuth may not be feasible with all MCP clients due to technical implementation differences. In such cases, use API key authentication instead.

API key authentication (evolve-mcp-key)

An API key is generated for a specific user context and supplied by the MCP client in the HTTP header evolve-mcp-key. There are two ways to generate an API key.

Method 1: Register a third-party client

Keys registered through the Third Party Clients page are bound to a System Account. System Accounts are same as System Runners defined for an Evolve application. All MCP client-to-server communication runs in the context of that System Account, which defines the SAP credentials, roles, and access rights used during tool execution. This method is not supported for the Studio Manager license type.

  1. In the Automate Evolve Administration App, go to Settings > Authentication > Third Party Clients.
  2. Click Register Client.
  3. In the sidebar, enter a name for the client.
  4. Set Client Type to MCPClient and Authentication Type to API Key.
  5. Select a System Account. Communication between the MCP client and MCP Server runs in the context of this System Account, which defines the SAP credentials, roles, and access rights used during tool execution.
  6. Click Save.
  7. Select the newly registered client and click View. Client Details sidebar opens.
  8. Click Show API Key to display and copy the API key.

Provide this key as the value for the evolve-mcp-key header when configuring an MCP client to connect to the MCP Server.

Method 2: Generate a personal MCP key from Personal Preferences

Each user can generate a personal MCP key from the Personal Preferences menu in the top-right menu bar of Automate Evolve. In the MCP Key section, copy the displayed key. To invalidate the current key and generate a new one, click the rotate icon next to the copy icon.

Note: To restrict MCP access to only keys registered through the Third Party Clients page, set the global workflow configuration key RestrictMCPClients to true. When this key is set, MCP clients using OAuth or a key generated from Personal Preferences are denied tool execution.

Authorization enforcement

The MCP Server enforces Automate Evolve permissions and authorizations at runtime. Only users with the relevant access rights can perform actions through MCP.

Evolve form views are respected by the MCP Server. When a solution has different views for different workflow stages, such as an originator view and a task view that expose different fields, the MCP Server presents only the fields available in the view applicable to the current user and workflow stage.

Known limitations

  • When Challenge on Approval is enabled for a workflow, task approval requires an interactive login and authentication step through the Automate Evolve application user interface. MCP clients do not support rendering user interface screens or handling the challenge login flow. Approvals for tasks that have Challenge on Approval enabled cannot be performed through MCP.