WTFM

Name: WTFM
Author: SupportPages-io

by SupportPages-ioversion 0.7.3i★ –iRuns on your computer

Registry nameio.github.SupportPages-io/wtfm

Install

Overview

Description from the maker (original English)

Your coding agent writes the user docs from your codebase, screenshots included.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "wtfm": {
      "command": "npx",
      "args": [
        "-y",
        "@supportpages.io/wtfm",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add wtfm -- npx -y @supportpages.io/wtfm mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "wtfm": {
      "command": "npx",
      "args": [
        "-y",
        "@supportpages.io/wtfm",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "wtfm": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@supportpages.io/wtfm",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SupportPages-io, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1396 servers in this category
Published to the registry more recently than 80% of the other 1396 servers in this category
Basic checks equal to or better than 100% of the other 1396 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is WTFM safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.3) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

WTFM

Write the F***ing Manual.

A plugin for your coding agent that writes the user docs. Screenshots included.

Install · Quick start · Examples · CLI · Publish · FAQ · Docs · Website

Real output from plausible/analytics , replayed fast. A real run takes a few minutes.

WTFM is a plugin for your coding agent that writes your user docs. Ask Claude Code or Codex for a guide and it reads your source, writes the steps in plain language, and shows every screen with a screenshot rendered from your real templates and CSS. No running app, no manual captures, no account.

Not API reference, not a README: docs for the people who will never read your code, like the customer who can't find the export button, or the admin inviting their team.

WTFM was formerly SupportPages Writer. The supportpages command still works as

an alias for wtfm, and existing installations, settings and SUPPORTPAGES_*

environment variables are unchanged.

Set it up once in your terminal, then just ask your agent:

curl -fsSL https://wtfm.sh/install | bash

wtfm setup          # once per computer

wtfm init           # once per project

You → Claude Code: Write an illustrated guide to inviting a teammate.

Features

Written from your source. Routes, button labels and flows come from the code, not from a description you type, so the steps match what users actually see.
Screenshots without running the app. Mockups are rebuilt from your own markup, styles and branding, then rendered to PNG in a local headless Chromium.
Plain Markdown output. Each article is an index.md with its images beside it, ready to commit next to your code or drop into any docs site.
Checked before it's saved. Every article passes structure, copy and screenshot checks first.
Uses the agent you already have. Claude Code or Codex, with your own subscription and model settings.
Local-first. Nothing is sent to SupportPages.io unless you choose to publish.

Examples

The same loop on other open-source codebases. Each image is one screenshot from a guide WTFM wrote from that repository's source; the apps were never run.

immich-app/immich · SvelteKit	paperless-ngx/paperless-ngx · Angular	maybe-finance/maybe · Rails

How to create a new album	How to create a tag and apply it to a document	How to add a new account

For a whole help centre, see WTFM's own docs: every article and screenshot there was written by WTFM from this repository.

Install

curl -fsSL https://wtfm.sh/install | bash

The installer downloads a checksum-verified release with its own Node.js, installs the wtfm command into ~/.local/bin (no sudo), and offers to add it to your PATH. It also installs supportpages as an alias for wtfm.

You'll need:

macOS or Linux, on ARM64 or x64 (on Windows, use WSL)
Claude Code or Codex, installed and signed in
Git

Chromium for screenshots is downloaded the first time you run wtfm setup.

Updating: releases check for updates once a day and install them in the background. Run wtfm update to update now, or set SUPPORTPAGES_AUTO_UPDATE=0 to turn automatic updates off.

Install in Codex

WTFM is also a Codex plugin. You'll need Node.js 22.12 or later with npm on your PATH.

codex plugin marketplace add SupportPages-io/wtfm

codex plugin add wtfm@supportpages

Then start a new Codex session. The first time the plugin starts, it installs its npm packages (without running their install scripts) and downloads Chromium for screenshots in the background. Codex asks you to review the plugin's two hooks in /hooks before they run; WTFM works without them. To update, run codex plugin add wtfm@supportpages again.

Build from source

You'll need Node.js 22.12 or later, npm and Git.

git clone https://github.com/SupportPages-io/wtfm.git

cd wtfm ./install-cli.sh

This builds your checkout and installs it as wtfm (with the supportpages alias). Run ./install-cli.sh again after pulling changes.

Quick start

Configure once in the terminal, then do everything else in your coding agent.

1. Set up your computer

wtfm setup

This connects Claude Code and/or Codex, adds the SupportPages.io writer to them and downloads the screenshot renderer. When it asks how you want to work, choose Save articles in my projects without an account.

2. Set up your project

cd path/to/your-product

wtfm init

Pick where articles should be saved and which model to use. WTFM then studies the project's structure, styles and branding once, so every article starts from that analysis.

3. Ask your coding agent

Open Claude Code or Codex in your project (restart any session that was already open) and ask for an article in plain words:

Write an illustrated guide to inviting a teammate.

A few minutes later the article is in your project:

output/articles/how-to-invite-a-teammate/

├── index.md ├── block_open-settings.png ├── block_invite-form.png └── block_send-invite.png

That's the whole loop. Some other things to ask:

What help articles do we have?

Write a troubleshooting article for when a sign-in link has expired.

CLI commands

You only need the terminal to set things up and keep them running. Writing happens in your coding agent.

Command	What it does
`wtfm setup`	Set up this computer: connect your coding agents and install the renderer
`wtfm init`	Set up this project: where articles go, which model, project analysis
`wtfm configure`	Change this project's agent, model, writing style or article folder
`wtfm analyse`	Re-run project analysis after big changes (`--refresh`)
`wtfm status`	Show this project's setup and article progress
`wtfm doctor`	Check that everything is installed and connected
`wtfm telemetry off`	Stop anonymous usage counts and crash reports (`on`, `status`)
`wtfm update`	Install the latest release
`wtfm uninit`	Forget this project's setup (keeps a recovery archive)
`wtfm remove`	Disconnect from your coding agents (keeps projects and articles)
`wtfm uninstall`	Remove WTFM from this computer; `--purge-config` also signs out and forgets project bindings

Run wtfm --help for every option. status and doctor accept --json.

Your articles

Where they go. output/articles/ / by default. To keep them in your repo, choose a folder like docs/help during init or with wtfm configure.
Writing style. Pick from friendly, minimal, technical or formal with wtfm configure.
Screenshots. Each article gets up to three. The main path gets them first; optional branches are described in text. Every screenshot carries a small "created automatically by supportpages.io" strip.

How it works

setup connects a local MCP server and a writer agent to Claude Code or Codex.
init has your agent map the project once: framework, routes, layouts, CSS and branding.
When you ask for an article, the writer agent reads the relevant source, writes the steps, and builds each screenshot as an HTML mockup of your real UI.
The mockups are rendered to PNG with a local Chromium, checked against your source, and saved with the article.

Publish

Give your users somewhere to read it. A Markdown folder in your repo helps nobody who can't find it. SupportPages.io, made by the same team, turns the guides WTFM writes into a help centre your users can search and ask: on your own domain, in your branding, and kept current as the product changes.

Kept current on every merge. When a pull request merges, SupportPages.io reads the diff and drafts the article updates for you to review.
Video walkthroughs. Each guide can come with a narrated video that clicks through the same steps, with captions.
Answers, not just search. Readers ask in their own words and get an answer drawn from your articles, with the sources linked.
Your branding on your own domain, an editor to review drafts before anyone sees them, and publishing straight from your coding agent.

Everything above works without it, and a free account hosts up to 10 articles.

The same pattern applies: connect once in the terminal, then work in your agent.

Connect a project:

wtfm publish

You'll sign in or create an account in your browser and choose a help centre. Any articles you've already saved upload as drafts. (Setting up a new project? Choose Publish them to a SupportPages.io help centre during wtfm init instead.)

Then keep asking your agent:

Write a guide to exporting a report.

New articles arrive in the help centre as drafts, with a link to review them in the editor. Publishing is always a separate step: click Publish in the editor, or ask:

Publish the guide to exporting a report.

Command	What it does
`wtfm publish`	Sign in, pick a help centre and upload this project's saved articles
`wtfm yolo`	Write the whole manual on SupportPages.io (account required; drafts only)
`wtfm login` / `logout`	Sign this computer in or out
`wtfm sync`	Refresh help-centre settings and article history

A help centre never needs access to your GitHub or Bitbucket. Only wtfm yolo does.

`wtfm yolo`: write the whole manual

Starting from nothing? wtfm yolo plans every guide your product needs and writes them all at once, on SupportPages.io's servers instead of your computer and your coding agent's usage.

wtfm yolo

It walks you through whatever is missing: browser sign-in, choosing or creating a help centre, and connecting your repository (SupportPages.io needs read access to write from your code). It then shows your plan's article allowance and asks before starting (--yes skips the question). The free plan covers your first 10 guides.

Progress shows live: sections, rec

Only the beginning is shown; read the rest in the repo

WTFM

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Features

Examples

Install

Install in Codex

Build from source

Quick start

1. Set up your computer

2. Set up your project

3. Ask your coding agent

CLI commands

Your articles

How it works

Publish

wtfm yolo: write the whole manual

`wtfm yolo`: write the whole manual