Set up Humanizer in about a minute.

Cursor

Open ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in one project. Add this, save, and check it shows as connected under MCP in Cursor settings.

{
  "mcpServers": {
    "humanizer": {
      "url": "https://mcp.makeaimorehuman.com/k/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Want the key out of the file? Use "Authorization": "Bearer ${env:HUMANIZER_KEY}" and set HUMANIZER_KEY in your shell profile.

Claude Code

Run this once in your terminal. --scope user makes it work in every project.

claude mcp add --transport http --scope user humanizer https://mcp.makeaimorehuman.com/k/mcp --header "Authorization: Bearer YOUR_KEY"

Check it with claude mcp list or /mcp inside Claude Code. You want a check mark next to humanizer.

Prefer JSON (for .mcp.json)? Remote entries need "type": "http" or Claude Code ignores them:

{
  "mcpServers": {
    "humanizer": {
      "type": "http",
      "url": "https://mcp.makeaimorehuman.com/k/mcp",
      "headers": {
        "Authorization": "Bearer ${HUMANIZER_KEY}"
      }
    }
  }
}

Claude Desktop

Claude Desktop runs local servers, so use the mcp-remote bridge. You need Node 18 or newer. Open Settings, then Developer, then Edit Config. That opens claude_desktop_config.json:

• Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "humanizer": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.makeaimorehuman.com/k/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_KEY"
      }
    }
  }
}

Fully quit and reopen Claude Desktop. No space after Authorization: on purpose. Some apps break args that contain spaces, so the space lives in the env value instead.

OpenClaw

Add it under mcp.servers in your OpenClaw config. Set transport to streamable-http. If you leave it out, OpenClaw tries SSE.

{
  "mcp": {
    "servers": {
      "humanizer": {
        "url": "https://mcp.makeaimorehuman.com/k/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer ${HUMANIZER_KEY}"
        }
      }
    }
  }
}

Set HUMANIZER_KEY in the gateway's environment, then run openclaw mcp doctor humanizer --probe to confirm it connects.

Hermes Agent

Add this to ~/.hermes/config.yaml and put HUMANIZER_KEY=YOUR_KEY in your profile's .env.

mcp_servers:
  humanizer:
    url: "https://mcp.makeaimorehuman.com/k/mcp"
    headers:
      Authorization: "Bearer ${HUMANIZER_KEY}"

Any other MCP client

Anything that supports remote MCP over Streamable HTTP with custom headers works. Windsurf, VS Code, Codex, Goose, LibreChat and custom agents all take some version of this:

{
  "humanizer": {
    "type": "http",
    "url": "https://mcp.makeaimorehuman.com/k/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_KEY"
    }
  }
}

Some clients call the type streamable-http or streamableHttp. If a client only runs local commands, use the mcp-remote bridge. Apps that only support OAuth sign-in for custom connectors (like the claude.ai web app or ChatGPT) are not supported yet.

Test it with curl

Step 1: say hello. You should get back "name":"humanization".

curl -s https://mcp.makeaimorehuman.com/k/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

Step 2: list the tools. You should see check_text and humanize_text.

curl -s https://mcp.makeaimorehuman.com/k/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

Step 3 (optional): score some text.

curl -s https://mcp.makeaimorehuman.com/k/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"check_text","arguments":{"text":"Moreover, we delve into cutting-edge solutions."}}}'

Use it

Ask your AI in plain words. For example:

• "Write the launch email, then run it through humanizer until it scores 90 or higher."
• "Check this paragraph with check_text and fix every block issue."

Want it on by default? Add one line to your project rules, CLAUDE.md, or AGENTS.md:

Before giving me any prose (emails, posts, docs, replies), run humanize_text, rewrite using its instructions, then confirm with check_text. Aim for 90+.

Troubleshooting

Text over 20,000 characters is rejected. Split long docs into sections.