Developer · Local MCP server

Workflowy

Create, update, complete nodes, search & replace with regex and dry run, usage reports, transforms.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.mholzen/workflowy
Version
0.8.1
Status
Active
Category
developer
Transport
stdio (local process)
Package
OCI image (Docker)
Published
2026-02-10
Updated
2026-02-10
Publisher
mholzen (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/mholzen) · how
Repository
github.com/mholzen/workflowy
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
OCI image (Docker)ghcr.io/mholzen/workflowy:0.8.1-stdioWORKFLOWY_API_KEY (required, secret)

How to connect Workflowy

Workflowy runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/mholzen/workflowy:0.8.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e WORKFLOWY_API_KEY ghcr.io/mholzen/workflowy:0.8.1. It reads the environment variable WORKFLOWY_API_KEY (required, secret); set it in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "workflowy": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "WORKFLOWY_API_KEY",
        "ghcr.io/mholzen/workflowy:0.8.1"
      ],
      "env": {
        "WORKFLOWY_API_KEY": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
WorkfileRepository-native protocol and local MCP server for Work, Docs, History and durable project Memory.Local · stdionpm: @illodev/workfile
Workflow GeneratorArchitecture diagram with concurrency capacity and bottleneck estimates from any codebase.Local · stdioPyPI: workflow-generator-mcp
Workflow MCPSession-bound Docker workflow server through Codex. State is discarded with the container.Local · stdioOCI image (Docker): docker.io/juliusolsson/workflow-mcp@sha256:4b688
Workflows MCP ServerStore, query, and create YAML workflow playbooks for LLM agents.Local · stdio, HTTPnpm: @cyanheads/workflows-mcp-server
WorkingMemoryPersistent personal memory for AI assistants - save, search, and recall across every MCP client.Remote · HTTPLive check: ✓ handshakeapp.workingmemory.ai
WORKMINEX402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers.Remote · HTTPLive check: ✓ handshakeworkmine-mcp.onrender.com
WORKS Public VerifierIndependent static verification for exact immutable public GitHub commits.Remote · HTTPLive check: ✓ handshakeworks-runner.vercel.app
Workspace ToolsSandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data.Remote · HTTPLive check: ✗ no handshakevandorla.com