Introducing AI2Human V6a & AI Detector 3A — our most advanced models yet

AI2Human MCP server

Connect Claude, ChatGPT, Cursor or your own AI agent to AI2Human. The agent can humanize text, detect AI writing and check your usage, using the plan you already have. There is nothing to install.

Server URL

https://ai2human.app/api/mcp

Transport: Streamable HTTP. Sign-in: OAuth 2.1 (for chat apps) or an API key (for agents and scripts).

Quick start

  1. Create a free AI2Human account at ai2human.app/auth/signup, or sign in.
  2. Add the server URL above to your AI app (steps for each app are below).
  3. Approve the connection when AI2Human asks, or paste an API key.
  4. Ask the agent: “Humanize this paragraph with AI2Human.”

Connect Claude (claude.ai and desktop)

  1. Open Claude and go to Settings, then Connectors.
  2. Choose “Add custom connector”.
  3. Paste the server URL exactly as shown above and continue.
  4. Click Connect. A page on ai2human.app opens: sign in if asked, then click Approve.

No API key is needed. Claude signs in through your AI2Human account.

Connect ChatGPT

  1. In ChatGPT settings, open the connectors (apps) section and add a custom connector or MCP server.
  2. Paste the server URL and choose OAuth as the sign-in method.
  3. A page on ai2human.app opens: sign in if asked, then click Approve.

Custom connectors in ChatGPT depend on your ChatGPT plan and may need developer mode switched on.

Connect Claude Code

Sign in through the browser:

claude mcp add --transport http ai2human https://ai2human.app/api/mcp

Then run /mcp inside Claude Code and choose ai2human to sign in. Or use an API key:

claude mcp add --transport http ai2human https://ai2human.app/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Connect Cursor, VS Code and other MCP clients

Add this to the client's MCP config file (for Cursor, .cursor/mcp.json):

{
  "mcpServers": {
    "ai2human": {
      "url": "https://ai2human.app/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Clients that support OAuth can leave out headers and sign in through the browser instead. Clients that only support local (stdio) servers can use the mcp-remote bridge with the same URL.

API keys (for agents and scripts)

  1. Sign in and open Dashboard, Settings.
  2. Under “AI agents (MCP)”, name a key and click Create key.
  3. Copy the key straight away. It is shown once and cannot be read again.
  4. Send it on every request as Authorization: Bearer YOUR_API_KEY.

You can hold up to 5 keys and revoke any of them from the same page. Keys start with a2h_sk_. Keep them out of source code and shared chats.

A raw request, for building your own agent:

curl -X POST https://ai2human.app/api/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_usage","arguments":{}}}'

Tools

humanize_text

Rewrites AI-generated text as natural human writing. Meaning, facts, figures and citations are kept. Charges one word per input word from the account's monthly words, then from any extra word packs.

  • text (required): the text to rewrite, up to the plan's words-per-call limit.
  • style (optional): standard (default), academic, formal, simple, informal, expand, shorten, email. Free accounts can use standard only.

Returns the rewritten text, then one line with the words charged, words remaining and our detector's human score for the result. A call can take up to 90 seconds. Free accounts wait about 20 extra seconds after their first few runs of the month.

detect_ai

Estimates how much of a text reads as AI-generated. Uses one of the account's monthly AI detector scans.

  • text (required): at least 20 characters. Longer text gives a more reliable result.

Returns aiPercentage, humanPercentage, wordCount and the scan counters. Paid plans also get sentences, each with a score and a level.

get_usage

Returns the plan, words used and remaining, the words-per-call limit and detector scans used. Takes no arguments and costs nothing. Agents should call it before humanizing long text.

Limits

MCP uses the same allowance as the website. There is no separate MCP plan or price.

PlanWords per monthWords per callDetector scans per month
Free2,0001305
Basic15,00060030
Pro50,0002,00070
Ultimate100,0005,000200

Each account can make 30 tool calls per minute. To humanize text longer than the words-per-call limit, split it at paragraph breaks and call humanize_text once per part. See pricing to raise the limits.

Errors

A failed tool call returns an error result whose text starts with a code, then a sentence saying what to do.

WORDS_PER_REQUEST_EXCEEDEDThe text is longer than the plan's words-per-call limit. Split it and call once per part.
USER_LIMIT_EXCEEDEDThe account does not have enough words left this month for this text.
STYLE_LOCKEDFree accounts can only use the "standard" style.
SCAN_LIMIT_REACHEDThe month's AI detector scans are used.
TEXT_TOO_SHORTdetect_ai needs at least 20 characters.
RATE_LIMITEDMore than 30 tool calls in a minute. Wait and retry.
TIMEOUT / ENGINE_FAILED / DETECTOR_FAILEDTemporary failure. No words were charged. Retry shortly.
USAGE_CHECK_FAILEDThe usage service could not be reached. Retry shortly.
UNAUTHORIZEDThe key was revoked or the app was disconnected. Connect again.

A request with no key or token, or an expired one, gets HTTP 401. OAuth clients then refresh or sign in again automatically.

Security and privacy

  • A key or connection can only call the three tools above. It cannot read your password, billing or settings.
  • Keys and tokens are stored only as hashes. We cannot show a key again after it is created.
  • Connected apps sign in with OAuth 2.1 and PKCE. Access tokens last one hour and renew automatically.
  • Disconnect an app or revoke a key at any time in Dashboard, Settings. It stops working immediately.
  • Text sent through MCP is handled like text entered on the website. See the privacy policy.

Notes for AI agents

  • Call get_usage first. Read wordsPerRequest and wordsRemaining.
  • Never send more than wordsPerRequest words in one humanize_text call. Split on paragraph breaks.
  • Send the text exactly as the user wrote it. Do not summarise or pre-edit it.
  • Return the humanized text to the user unchanged. Rewriting it again undoes the result.
  • On USER_LIMIT_EXCEEDED or SCAN_LIMIT_REACHED, stop and tell the user. Retrying will not help.
  • Allow up to 120 seconds for humanize_text before treating a call as failed.

OAuth discovery: /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server on this domain. Dynamic client registration is supported.

Troubleshooting

  • The app says it cannot connect. Check that the URL is exactly https://ai2human.app/api/mcp, with https and no trailing slash.
  • The approval page says the request is not valid. Remove the connector in your AI app and add it again.
  • A key stopped working. It was revoked, or the account was removed. Create a new key in Settings.
  • Still stuck? Contact us and include the error code.