Skip to main content
Bring StealthGPT into your Codex workflow to humanize product copy, articles, and other drafts without switching to a separate editor. Connect once with your StealthGPT account, then ask Codex to submit a rewrite and retrieve the result through MCP.

​
Connect with OAuth

You need the Codex CLI and a StealthGPT account with available subscription usage or API credits. OAuth handles sign-in, so you don’t need to copy an API key.
1

Add the StealthGPT MCP server

Run this command in your terminal:
2

Sign in with your StealthGPT account

Start the OAuth flow:
Open the sign-in page when prompted, sign in, and approve the connection.
3

Open a Codex session

Start a new Codex session so it loads the connection. The StealthGPT tools are available alongside your other MCP tools.
For Codex installation and MCP configuration options, see the official Codex MCP guide.

​
Humanize a draft

Give Codex the text and the workflow you want. For example:
humanize_text starts an asynchronous job and returns a runId. Codex uses get_run_status with that same ID to retrieve its progress and completed result. Keep the ID for the existing run instead of submitting the draft again while it is processing. MCP humanization defaults to model: "super" and outputFormat: "markdown". The example selects plain text explicitly. For content with headings, links, or tables, use the text-preservation guide to plan format-sensitive requests and review the returned structure before saving it to a file.

​
Choose the right tool

  • humanize_text rewrites text you already have. Choose super, standard, or lite and a quality mode for the task.
  • generate_content starts a Stealth Agent content workflow from a brief, using an academic, seo, or social preset.
  • get_run_status retrieves progress and results for either kind of run.
See the MCP tool reference for arguments, defaults, and result fields, and workflow patterns for larger publishing pipelines.

​
Account and usage

Runs are billed to the StealthGPT account used during OAuth sign-in. Subscription usage and API-credit selection follow the MCP billing rules; check those rules and your account settings before starting a larger batch. The OAuth connection does not require a separate API token.
Setup verified November 7, 2026 with codex-cli 0.167.0-alpha.3.2: OAuth sign-in completed, and the connected desktop client completed a humanize_text → get_run_status flow.