Automation Weaver

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

No-code workflow visualizer and automation blueprint builder.

VerifiedSSEWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint for visualizing no-code workflows and building automation blueprints.

What you can do
  • The server is described as a no-code workflow visualizer and automation blueprint builder, so an assistant can help lay out and visualize automation flows and assemble blueprint-style plans for them.
  • No tool list is published, so the exact operations available are not documented; expect workflow design and visualization support rather than a known set of named tools.
  • Premium settlement is mentioned, implying some features are gated behind a paid step.
When to use it
Consider it when you want an assistant to help sketch, visualize or blueprint no-code automation workflows, and you are comfortable connecting to a hosted third-party endpoint.
Requirements
A remote SSE endpoint at the provider's hosted address; no local package or runtime is needed. No authentication is declared, but premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The payment-signature header is a cryptographic authorization signature tied to a blockchain payment scheme; treat it as a spending credential and only supply it for premium settlement you intend to pay. No tool list or README is published, so what the server does with your workflow data is unclear, and workflow content is sent to a third-party host.

Installation

In SourceWeft

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

Web executable via SSE. 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.Evozim%2Fautomation-weaver/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": {
    "automation-weaver": {
      "type": "sse",
      "url": "https://automation-weaver-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.