Use WROITER where you already write.

WROITER runs as a tool inside the AI you already use, or as an API in your own pipeline. It reads your text and hands back specific fixes — the same engine this site runs. Pick your setup below. No account. Your draft isn’t saved.

Claude

Verified

Add WROITER as a custom connector. Works on Claude Free (one connector), Pro, Max, Team, and Enterprise.

https://api.wroiter.com/mcp
  1. In Claude, open Customize → Connectors and choose Add custom connector (or Add → Custom → Web).
  2. Name it WROITER, paste the URL above, and choose No sign in for authentication.
  3. Open a chat, switch the WROITER connector on, and paste a draft (15 words or more).
  4. Ask: “Run this through WROITER and apply the fixes.”

You'll know it worked when Claude calls the wroiter_revise tool and answers with named fixes — what to change, where, and why — instead of a vague rewrite.

On Team or Enterprise, your workspace may need an owner to add the connector first. Claude’s current connector instructions.

Stuck? admin@wroiter.com

ChatGPT

Custom MCP plugin

Add WROITER as a custom MCP plugin in ChatGPT on the web. Availability depends on your account and workspace permissions. If you cannot add a plugin, use the browser diagnostic and paste its revision prompt into your chat.

WROITER reads the draft you send and returns revision instructions. It does not edit your files or publish anything. Review ChatGPT’s connection warning and the text you share with the tool.

https://api.wroiter.com/mcp
  1. Open Plugins in ChatGPT on the web. Select the plus button, then Add custom MCP server.
  2. Name it WROITER, enter the URL above under Connection, and choose No authentication.
  3. Review the warning, create the plugin, and install it. In a chat, type @ to select WROITER, then paste a draft (15 words or more).
  4. Ask: “Run this through WROITER and apply the fixes.”

You'll know it worked when ChatGPT calls wroiter_revise and returns the same per-instance fixes.

OpenAI’s current custom MCP setup instructions.

Stuck? admin@wroiter.com

Any other tool

For Gemini, Grok, a script, or a content pipeline — reach the same engine over MCP or plain HTTP.

Any MCP client

Point any MCP-capable client (Claude Desktop, Cursor, an agent) at the same URL. The tool is wroiter_revise.

https://api.wroiter.com/mcp
The HTTP API

For pipelines and anything that isn't MCP. One POST, no key.

POST https://api.wroiter.com/revise Content-Type: application/json { "text": "your draft — 15 words or more" }

It returns { payload, markdown } — payload is the structured findings, markdown is a revision prompt you can paste into any AI. Up to 100,000 characters, about 20 requests a minute.

Teams drop this between drafting and review as an automatic de-slop pass — the editor opens a cleaned draft instead of catching slop by eye.

Gemini, Grok, Perplexity and more get their own walkthroughs as we verify each one. Until then, the API reaches them all.

Make ChatGPT or Claude fix the actual AI slop.

“Make it sound human” gives your AI another vague instruction. Give it the draft and the specific fixes instead.

  1. Use a draft you need to edit. With WROITER connected, ask your AI to call wroiter_revise on it. Check the tool call rather than assuming a rewrite means the tool ran.
  2. Read one finding. For example, “it’s important to note” can delay the claim. The revision instruction tells the AI to start with the claim itself. Keep a phrase if the context gives it a real job.
  3. Apply the useful instructions. Ask: “Apply WROITER’s revision instructions to this draft. Preserve the facts, meaning, and voice. Leave unrelated passages alone. Show me what you changed.”
  4. Review the revision. Check that it still says what you meant. Fewer findings alone do not prove better writing.

No connector? Open the free diagnostic, paste the same draft, and choose Find patterns & fixes. If revision instructions are available, choose Copy full prompt and paste it alongside your draft into your AI. Nothing flagged means there may be no prompt to copy.

However you connect, the answer is specific.

Paste a draft and WROITER returns one instruction per problem — the phrase, the fix, and the reason. Here's a real response, with three of its flags.

AI-typical phrase template BANNED_PHRASES high confidence

Findit's important to note

ActionDelete "it's important to note" and start the sentence with the substantive claim that follows. If the sentence has nothing left after the deletion, the sentence had nothing to say.

WhyTemplate phrases defer commitment to a specific claim. Detectors flag them at the lexical level and editors flag them at the reading level; removing them sharpens both at once.

Credibility-asserting framing CREDIBILITY_THEATER high confidence

FindLet me be direct

ActionDelete the framing and make the direct statement itself. Honest writing doesn't announce its honesty; the label only advertises the gap.

WhyPermission-asking and credibility labels are persona leakage — the writing performing a posture instead of carrying the point.

Sequence-marker scaffolding OVER_SIGNPOST high confidence

FindFirst

ActionRemove "First". The reader can see this is the next paragraph; they don't need a label that says so. If the order matters, the content carries it.

WhyStacked sequence markers ("First … Second … Finally") signal essay scaffolding that survived into the final draft.

…and the rest, grouped by severity. Every flag carries a confidence badge — high means the fix is mechanical, medium means it's your editorial call.

  • No LLM call and no model spend — the engine is deterministic pattern-matching, not a guess.
  • WROITER processes your text for the request and does not persist the submitted text or result.
  • Same text in, same findings out, every time.
  • It's the exact engine running on this site, behind a URL.
The full method is published →