GPTHuman-Humanizer
OfficialGPTHuman MCP Server
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.
Quick Start
You can run the server directly and test it in 60 seconds:
export GPTHUMAN_API_KEY=...
npx -y @gpthuman/mcp-serverTo test the server interactively with the MCP Inspector before wiring it up to Cursor or Claude:
npx @modelcontextprotocol/inspector npx -y @gpthuman/mcp-serverRelated MCP server: AI Humanizer MCP Server
Requirements
Node.js
>= 22.0.0A GPTHuman API key — get one at GPTHuman.ai
Configuration
The server reads a single environment variable:
Variable | Required | Description |
| Yes | Your GPTHuman API key. |
Installation
Cursor
Add the server to ~/.cursor/mcp.json (or your workspace .cursor/mcp.json):
{
"mcpServers": {
"gpthuman": {
"command": "npx",
"args": ["-y", "@gpthuman/mcp-server"],
"env": {
"GPTHUMAN_API_KEY": "your-api-key-here"
}
}
}
}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.
Claude Desktop
Add it to claude_desktop_config.json:
{
"mcpServers": {
"gpthuman": {
"command": "npx",
"args": ["-y", "@gpthuman/mcp-server"],
"env": {
"GPTHUMAN_API_KEY": "your-api-key-here"
}
}
}
}Other clients
Any MCP client that supports the stdio transport can run the server with:
GPTHUMAN_API_KEY=your-api-key-here npx -y @gpthuman/mcp-serverTools
humanize_text
Transforms 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 |
| string | Yes | — | The text to humanize. Must be at least 300 characters and at most 2,000 words. |
| enum | No |
| Target reading level / tone. One of |
| enum | No |
| Rewrite strategy. One of |
Output
The tool returns two content blocks:
The humanized text (the primary payload).
A markdown summary with metadata: AI-detector human score, similarity to original, readability, detected language, applied tone and mode, input/output word and character counts, credit usage, remaining credit balance, and the request ID.
Example call (from an MCP client)
{
"name": "humanize_text",
"arguments": {
"text": "Your AI-generated text of at least 300 characters goes here...",
"tone": "College",
"mode": "Balanced"
}
}Example Output
---
**Metadata Summary:**
- **Human Score:** 98%
- **Similarity:** 85%
- **Readability:** College-level
- **Credit Usage:** 142
- **Remaining Balance:** 4,858
- **Request ID:** req_xyz123Example Prompts for MCP Clients
Once the server is configured, try giving your AI agent prompts like:
“Humanize this generated blog intro in College tone using Balanced mode.”
“Rewrite this product description in Professional mode.”
“Use Enhanced mode but preserve the original meaning.”
Use the Remote MCP Endpoint
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.
Endpoint
https://api.gpthuman.ai/mcp
List available tools
Use tools/list to inspect the tools exposed by the GPTHuman MCP server.
curl --location 'https://api.gpthuman.ai/mcp' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data '{
"jsonrpc": "2.0",
"method": "tools/list",
"id": 1
}'Humanize text
Use tools/call with the humanize_text tool to transform AI-generated text into more natural, human-sounding writing.
curl --location 'https://api.gpthuman.ai/mcp' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "humanize_text",
"arguments": {
"text": "Your AI-generated text of at least 300 characters goes here...",
"tone": "DESIRED_TONE",
"mode": "DESIRED_MODE",
"apiKey": "YOUR_GPTHUMAN_API_KEY"
}
}
}'Parameters
text: The text you want to humanize.tone: The writing tone to use, such asCollege,Professional, or another supported tone.mode: The humanization mode, such asBalanced.apiKey: Your GPTHuman API key.
When to use this option
Use the remote MCP endpoint if you are building:
custom AI agents
backend automations
workflow integrations
internal writing tools
no-code or low-code connectors
systems where running a local MCP server is not practical
For desktop MCP clients like Claude Desktop, Cursor, or Windsurf, you can still use the local MCP server setup shown above.
Credit Usage & Privacy
Credit Usage: Credits are consumed per word of output generated.
Privacy: Submitted content is private and is not used for retraining AI models.
Troubleshooting
401: Invalid or missing API key. Verify your
GPTHUMAN_API_KEYis set correctly.400: The text provided is under 300 characters or over 2,000 words.
429: Rate limit exceeded or insufficient credits.
Node version issue: Ensure you are using Node >=22.
humanScore: null: The detector score is unavailable for that specific language or content type.
Development
git clone https://github.com/GPTHuman-ai/mcp-server.git
cd mcp-server
npm install
cp .env.example .env
# Edit .env and set GPTHUMAN_API_KEY
npm run build
npm startAvailable scripts:
Script | Description |
| Compile TypeScript to |
| Run the compiled server on the stdio transport. |
| Format the codebase with Prettier. |
| Run the Jest test suite. |
Project structure
src/
stdio.ts Entry point — wires the server to the stdio transport.
McpServerFactory.ts Builds the McpServer and registers tools.
GptHumanAPI.ts Wrapper around the GPTHuman REST API.
HttpsClient.ts Thin axios wrapper with auth and timeout.
type.d.ts Shared request/response interfaces.Links
License
Apache-2.0 — see LICENSE.
Available Tools
1 toolhumanize_textHumanize TextAInspect
Transforms AI-generated text into a more natural, human-sounding variant while preserving the requested tone and rewrite mode. Input must be at least 300 characters and must not exceed 2,000 words.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Optional rewrite mode. Defaults to `Balanced` when omitted. | |
| text | Yes | The text to humanize. Must be at least 300 characters and must not exceed 2,000 words. | |
| tone | No | Optional tone for the rewritten text. Defaults to `College` when omitted. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds context beyond annotations by stating that the tool 'preserves the requested tone and rewrite mode,' indicating behavioral consistency. Annotations already indicate non-read-only and non-destructive, but the description further clarifies the nature of the transformation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences: one for purpose and one for constraints. No redundant information, every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no output schema, the description covers purpose, constraints, and preservation details. It lacks return value information but is otherwise complete given the complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all parameters. The description adds meaning by linking 'tone' and 'mode' to the preservation behavior, reinforcing their role beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: transforming AI-generated text into a more natural, human-sounding variant while preserving tone and rewrite mode. It uses a specific verb ('transforms') and resource ('AI-generated text'), and distinguishes itself from potential siblings (none listed).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes explicit input constraints: at least 300 characters and at most 2,000 words. This provides clear guidance on when to use the tool. However, it does not give comparative guidance against alternatives, though no siblings exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.4- First observed
humanize_text
TDQS
Only one tool exists, so there is no risk of confusion between tools.
With a single tool, naming consistency is trivially perfect; the name 'humanize_text' is clear and follows a verb_noun pattern.
The server offers only one tool, which feels thin for a server dedicated to humanizing text; additional tools like detection or tone adjustment would be expected.
The tool covers basic humanization but lacks other expected operations such as tone selection, style conversion, or AI text detection, leaving significant gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Rewrite AI-generated text so it reads as human, in a persona's voice.
Humanize AI-written English. Facts and length kept. Paid per successful run over x402 (testnet).
Score and rewrite AI-assisted prose while preserving names, numbers, quotes, links, and facts.
1199Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free.
Related MCP Servers
- AlicenseCqualityDmaintenanceHelps refine AI-generated content to sound more natural and human-like. Built with advanced AI detection and text enhancement capabilities.15059MIT
- AlicenseCqualityDmaintenanceDetects AI-generated content and transforms robotic text into natural, human-like writing while improving grammar, readability, and preserving key terminology.1503MIT
- FlicenseNot gradedqualityNot gradedmaintenanceHumanizer PRO - The Best AI Text Humanizer MCP Server Transform AI-generated content into natural, human-sounding text that bypasses GPTZero, Turnitin, Originality.ai, Copyleaks, ZeroGPT, and other AI detectors. Undetectable AI content rewriting with Stealth, Academic, and SEO modes.3-
- AlicenseNot gradedqualityDmaintenanceEnables transforming AI-generated marketing copy into human-sounding, GEO-optimized content for AI search engines.40MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GPTHuman-ai/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server