Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stealthgpt.ai/llms.txt

Use this file to discover all available pages before exploring further.

StealthGPT ships a remote MCP (Model Context Protocol) server, so AI agents and MCP-aware clients can generate and humanize content as a tool — without you writing any integration code. This is the agent / tool invocation workflow pattern: the model decides when to call the tools and you stay inside your editor or chat.
One server, many clients. The same MCP server works with Cursor, Claude, ChatGPT, and any MCP-compatible runtime. You don’t install a per-client plugin.

​
Server endpoint

https://stealthgpt.ai/api/mcp/mcp
Transport: Streamable HTTP (the modern MCP transport). A legacy SSE endpoint is also available at /api/mcp/sse.

​
Authentication

Today the server authenticates with your Stealth API token sent as a bearer header: 
Authorization: Bearer YOUR_API_TOKEN
Get your token from the Stealth API dashboard.
Clients that let you set a custom header (for example Cursor) work today with the bearer token above. One-click connectors inside claude.ai (web) and ChatGPT use OAuth and are coming soon.

​
Tools

ToolPurposeKey arguments
generate_contentStart a full Stealth Agent run (research → draft → optional fact-check → humanize → optional images).preset (academic | seo | social), prompt, platform (for social), enableFactCheck, enableImageGeneration
humanize_textStart a humanization run for existing text.text, qualityMode (fast | quality), model (heavy | lite), outputFormat (text | markdown)
get_run_statusGet the current status and final result of a run.runId
generate_content and humanize_text return a runId immediately (the work runs asynchronously). The agent then calls get_run_status with that runId until the status is completed, failed, or cancelled.
On a completed humanization, howLikelyToBeDetected is a 0–100 human-likeness score where higher is better (more human, less likely to be flagged as AI).

​
Install

One-click for Cursor: Add to Cursor
The one-click button adds the server URL; until OAuth ships you still add your Authorization: Bearer YOUR_API_TOKEN header in the generated mcp.json. After OAuth, connecting will be fully one-click (no token to paste).
Or configure manually for your client:
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global), then reload MCP servers:
{
  "mcpServers": {
    "stealthgpt": {
      "url": "https://stealthgpt.ai/api/mcp/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_TOKEN" }
    }
  }
}
Once connected, the three tools appear in the client and the agent calls them when relevant — for example:
Humanize this paragraph: …
or
Generate an SEO article about home solar energy.

​
Example flow

  1. The agent calls humanize_text with your text → receives { "runId": "…", "status": "queued" }.
  2. The agent polls get_run_status with that runId.
  3. When status is completed, it returns the humanized result, howLikelyToBeDetected, and billing fields (wordsSpent, creditsSpent, remainingCredits, billingMode, meteredChargedCredits).

​
Claude & ChatGPT

The same server will be connectable directly inside claude.ai (web) (Settings → Connectors → Add custom connector) and ChatGPT via OAuth — letting users generate humanized, undetectable text without leaving the LLM. These flows require OAuth and are in progress.

​
Notes & limits

  • Runs are billed to the account that owns the API token, using the standard word-based billing.
  • Generation can take from seconds (humanize-only, lite) to a few minutes (full academic/seo pipeline). Because it’s async, the tool call returns quickly and the agent polls.
  • See the async workflow and Stealth Agent async runs pages for the underlying REST contract.