HumanifyMe MCP server
io.github.JoshMcQ/humanifyme·v0.2.2Learns your writing voice locally and rewrites AI drafts so they sound like you.
0 stars6 downloads/wk
Reviews
Write oneNobody has reviewed HumanifyMe yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
HumanifyMe tools (16, 4 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
humanify_add_sampleStore a writing sample (something the user actually wrote) so HumanifyMe can learn their voice. Text must be at least 100 characters and carry at least one context label.
humanify_audit_listList the most recent outbound requests HumanifyMe made (metadata only, never content): provider, route, payload size, draft length, success.
humanify_build_profileBuild (or rebuild with force:true) the user's style profile from their stored samples. Needs at least 3 samples. Samples are redacted before being sent to the configured LLM provider.
humanify_delete_profilewrite actionDelete the current style profile. Samples are kept.
humanify_delete_samplewrite actionDelete a stored writing sample by id.
humanify_get_profileReturn the user's current style profile, or null if none has been built.
humanify_import_chat_exportImport writing samples from a ChatGPT or Claude data-export (.zip, conversations.json, or extracted directory). Only user-authored turns are kept; code-heavy turns are dropped; everything is redacted before storage. Call with commit:false first to preview 5 samples, then commit:true.
humanify_import_text_filesBulk-import writing samples from a directory (or single file) of .txt/.md/.docx the user wrote \u2014 notes, blog drafts, an Obsidian vault. Requires a default context label. Files are redacted before storage; oversize files split at paragraph boundaries.
humanify_list_samplesList stored writing samples (previews truncated to 200 chars).
humanify_metricsShow how well HumanifyMe is matching the user's voice, from their own recorded feedback: total rewrites, accept/edit/reject rates, "sounds like me" breakdown, per-context and per-provider counts, and p50/p95 latency. Local only; counts, never content. Optional `since` (ISO timestamp) windows the stats.
humanify_record_feedbackRecord whether a humanify_text rewrite sounded like the user. Pass the feedbackToken from that rewrite and a signal: 'accept' (sounded like me / used as-is), 'edit' (kinda \u2014 I tweaked it), or 'reject' (no \u2014 didn't sound like me). Optional short reason. This powers local quality metrics (humanify_metrics) and, only if the user opted in, anonymous aggregate counts.
humanify_set_providerConfigure local Ollama and make it the default. Cloud API keys are intentionally rejected in MCP tool arguments because the host model can see them; configure cloud providers with the interactive `humanifyme setup` CLI instead.
humanify_test_keyConfirm the configured API key works with a cheap (\u22641 token) ping.
humanify_textRewrite a draft (usually AI-generated) so it reads in the user's own voice, using their stored style profile. The headline tool: call this whenever the user wants text to 'sound like me' or 'less AI'.
humanify_update_profilewrite actionReplace the style profile with an edited version (schema-validated). Use for manual tweaks; does not call any LLM.
humanify_wipe_allwrite actionDelete ALL HumanifyMe data: samples, profile, cache, audit log. Irrevocable. Requires confirm: "DELETE EVERYTHING".
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How HumanifyMe compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 16
- the typical server has 7
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 6
- more than 1% of 12,191 servers with a package
What its tools let an agent do: 12 read · 4 change
Install HumanifyMe in Claude Code, Cursor or VS Code
Runs npx -y humanifyme on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add humanifyme -- npx -y humanifyme
What the publisher says
From the HumanifyMe repository's README, as published. We do not edit it. Read it on GitHub
HumanifyMe
Make AI sound like you. · humanifyme.com
Try it in your browser → No install and no key: paste a few of your own messages and an AI draft, and get the draft back in your voice.
HumanifyMe learns how one specific person writes, then rewrites an AI agent's output in that person's voice before anyone reads it. Install it once and every agent on your machine — Claude Code, Cowork, Cursor — rewrites in the same voice. It is not "write better." It is "stop sounding like AI."
It runs locally. The only thing that crosses the network is a redacted draft sent to the LLM provider you choose.
Quickstart
Run the secure one-time setup first. It explains the privacy boundary, hides your provider key while you type it, validates the provider, collects three writing samples, builds your profile, and offers a first rewrite:
npx -y humanifyme@0.2.2 setupWant to see it work before installing? A live demo of the setup and rewrite flow is at humanifyme.com.
Never paste a provider key into an AI chat or pass it as a command-line flag. Then install the plugin from the bundled marketplace — no clone or build:
claude plugin marketplace add JoshMcQ/HumanifyMe # register the marketplace
claude plugin install humanifyme@humanifyme # installs 3 skills + the MCP serverThen use /humanifyme:humanify on any draft, or let the bundled skills trigger it after an agent drafts an email, PR, or message. The CLI and every installed agent share the profile stored in ~/.humanifyme/. Use /humanifyme:build-voice-profile later to add samples or rebuild it.
Tried it? Rate a rewrite: two dropdowns, and it is the feedback that improves voice matching most.
Run /reload-plugins if you installed mid-session. Using a different agent (Cursor, Continue, Cline, Windsurf, Zed, ChatGPT desktop) or the CLI? See Install.
Want to inspect a draft before setting up a profile? The analyzer is local, deterministic, and needs no API key:
echo "At its core, this robust approach paves the way." | npx -y humanifyme analyzeIt reports the exact phrases and punctuation it matched against the public 90-sign AI-writing checklist. It is an editing aid, not an AI detector; subjective signs stay labeled for human review instead of being turned into a fake probability.
Why it exists
People hand more of their writing to AI every day — commits, PR descriptions, Slack posts, email drafts — and every agent produces the same recognizable register: polished, balanced, faintly corporate. Recipients have learned to spot it. The usual fixes (Grammarly, Wordtune, "AI humanizers") push text toward a generic professional voice, which is the opposite of the goal.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
HumanifyMe: common questions
- Is HumanifyMe MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the HumanifyMe safety report
- How do I install HumanifyMe?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does HumanifyMe need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is HumanifyMe maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.2.
- How does HumanifyMe compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.