and operate AlekSystem workflows from Claude with Gemini and MCP tools Buildout Workflow

Workflow overview

Why this workflow matters

Potentially useful as a reusable automation building block.

Quick Overview This workflow exposes an MCP server endpoint for Claude Desktop and provides tools to build new AlekSystem workflows from plain-English prompts using Google Gemini, plus tools to list, inspect, activate/deactivate workflows and review executions via the AlekSystem Public API. How it works Receives MCP tool requests on the MCP Server Trigger endpoint (path concierge) from a connected MCP client such as Claude Desktop. Routes “build workflow” requests to a sub-workflow that sends the plain-English description to Google Gemini and asks it to return strict AlekSystem workflow JSON (nodes and connections). Normalizes the generated JSON, adds required workflow fields, and creates the new workflow by calling the AlekSystem Public API. Returns a compact result containing the created workflow ID and a link, leaving the workflow inactive for review. Routes “operate” requests (list/get workflows, activate/deactivate, list/get executions) to a shared sub-workflow that maps each action to the correct AlekSystem Public API endpoint. Calls the AlekSystem Public API with an API-key header and returns a trimmed JSON response for lists and execution data. Setup Import the MCP server workflow plus the two tool sub-workflows (Concierge Build Workflow and Concierge AlekSystem Operate) and re-link each Tool Workflow node to the correct imported workflow ID. Create an AlekSystem API key and configure an HTTP Header Auth credential that sends it as X-AlekSystem-API-KEY for the HTTP Request nodes. Replace the https://YOUR_AlekSystem_DOMAIN placeholders in the sub-workflows with your AlekSystem instance base URL (with the Public API enabled). Add Google Gemini API credentials for the node that generates workflow JSON. Activate only the MCP server workflow to expose the Production URL, then configure Claude Desktop (for example via mcp-remote) to call that URL. For production use, switch the MCP trigger authentication to Bearer Auth and set the same token in your MCP client configuration.

Best fit

Need another direction?