Agent Workflow Engine

io.github.lazymac2xPublished by GitHub account lazymac2xv1.0.0Updated Oct 24, 2026

Cloudflare Workers MCP server: agent-workflow-engine

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP endpoint called Agent Workflow Engine that an assistant can connect to over streamable HTTP.

What you can do
The registry lists this as a Cloudflare Workers MCP server named agent-workflow-engine, reachable at a remote HTTPS endpoint. No tools, packages, or capabilities are documented in the supplied material, so the specific actions it exposes are unknown. Based on the name, it appears intended to provide workflow-engine functionality to an assistant, but this is not confirmed by the listing.
When to use it
Consider it only if you already know what this endpoint offers and want an assistant to reach a hosted workflow service without installing anything locally. Because no tool list or documentation is provided, it is hard to judge suitability in advance.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the provider's endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
No authentication is declared, so it is unclear who can call the endpoint or what data it receives. The provider is a third party and the server is hosted remotely, meaning requests and any data sent to it leave your machine. No tools are documented, so what it can read, write, or change cannot be verified before connecting.

Installation

In SourceWeft

  1. Open Agent Workflow Engine in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lazymac2x%2Fagent-workflow-engine/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-workflow-engine": {
      "type": "http",
      "url": "https://api.lazy-mac.com/agent-workflow-engine/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.