The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Humanizer listing page.
A Model Context Protocol (MCP) server providing access to GPTHuman's API, the leading platform for rewriting AI-generated text into more natural, human-sounding prose, with AI-detector metadata returned when available. This allows any MCP-compatible client (Cursor, Claude Desktop, etc.) to call the humanizer tool natively.
The server is shipped as a single humanize_text tool that rewrites AI-generated text into a more natural, human-sounding variant, while preserving the requested tone and rewrite mode.
You can run the server directly and test it in 60 seconds:
To test the server interactively with the MCP Inspector before wiring it up to Cursor or Claude:
>= 22.0.0The server reads a single environment variable:
| Variable | Required | Description |
|---|---|---|
GPTHUMAN_API_KEY | Yes | Your GPTHuman API key. |
Add the server to ~/.cursor/mcp.json (or your workspace .cursor/mcp.json):
Security Note: While the example above places the
GPTHUMAN_API_KEYdirectly in JSON, we recommend using environment variables or local secret storage when possible. Never commit.cursor/mcp.jsonwith real API keys to version control.
Add it to claude_desktop_config.json:
Any MCP client that supports the stdio transport can run the server with:
humanize_textTransforms AI-generated text into a more natural, human-sounding variant designed to bypass AI detectors, while preserving the requested tone and rewrite mode.
Input parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
text | string | Yes | — | The text to humanize. Must be at least 300 characters and at most 2,000 words. |
tone | enum | No | College | Target reading level / tone. One of Standard, HighSchool, College, PhD. |
mode | enum | No | Balanced | Rewrite strategy. One of Professional, Balanced, Enhanced. |
Output
The tool returns two content blocks:
Example call (from an MCP client)
Example Output
Once the server is configured, try giving your AI agent prompts like:
If you don’t want to run the MCP server locally, you can call GPTHuman’s hosted MCP endpoint directly over HTTP using JSON-RPC 2.0. This is useful for custom agents, backend workflows, automation platforms, or internal tools that want to integrate GPTHuman without managing a local MCP process.
https://api.gpthuman.ai/mcp
Use tools/list to inspect the tools exposed by the GPTHuman MCP server.
Use tools/call with the humanize_text tool to transform AI-generated text into more natural, human-sounding writing.
text: The text you want to humanize.tone: The writing tone to use, such as College, Professional, or another supported tone.mode: The humanization mode, such as Balanced.apiKey: Your GPTHuman API key.Use the remote MCP endpoint if you are building:
For desktop MCP clients like Claude Desktop, Cursor, or Windsurf, you can still use the local MCP server setup shown above.
GPTHUMAN_API_KEY is set correctly.humanScore: null: The detector score is unavailable for that specific language or content type.Available scripts:
| Script | Description |
|---|---|
npm run build | Compile TypeScript to dist/. |
npm start | Run the compiled server on the stdio transport. |
npm run format | Format the codebase with Prettier. |
npm test | Run the Jest test suite. |
Apache-2.0 — see LICENSE.