Class ProcessesMcpTool

java.lang.Object
org.exoplatform.processes.mcp.ProcessesMcpTool
All Implemented Interfaces:
io.meeds.mcp.server.plugin.McpToolPlugin

@Service @Profile("mcp-server") public class ProcessesMcpTool extends Object implements io.meeds.mcp.server.plugin.McpToolPlugin
MCP tools exposing the eXo Processes add-on to the AI agent (EVA).

A process type (WorkFlow) is backed by a Task/Kanban project (WorkFlow.projectId); a request (Work) IS a task (Work.taskId) whose status is the task's Kanban column (default columns: Request, RequestInProgress, Validated, Refused, Canceled).

Every method acts as the current user: the current user's social identity id is resolved and passed to the self-scoping ProcessesService calls (getWorks / getWorkById filter by createdBy), so platform ACLs are enforced.

Approver actions ride the existing Task MCP tools by design: to respond to a pending request, the agent calls the eXo Task tools on the request's task id (update_task_status to Validated/Refused, add_task_comment). This class deliberately does NOT duplicate that task-write path; it only surfaces the pending requests to act on via getPendingApprovals().