Alchemy MCP Server

MCP server that serves the Alchemy ruleset to any agent, so it writes human-quality prose instead of tell-tale LLM text. Exposed over MCP by the alchemy mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Alchemy is a drop-in ruleset that stops your AI coding agent from writing like an LLM: no em-dash pile-ups, no "not just X, it's Y", no stray delve. You add it once, your agent reads it before it writes, and the READMEs, commits, and docs it produces start sounding like a person wrote them.

Its toolset

Everything the assistant can do here goes through one of these:

• Throat — clearing openers ("In today's fast-paced world", "At its core") and recap closers ("In conclusion", "Ultimately")
• PyPI — alchemy-writing — pip install alchemy-writing
• MCP — @fernforge/alchemy-mcp — npx @fernforge/alchemy-mcp

Adding it to your client

@fernforge/alchemy on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

When to reach for it

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Alchemy's toolset — Throat, PyPI, MCP — is a fair guide to whether it matches your workflow. It is maintained by fernforge; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the alchemy mcp server does with a few real requests.