Your voice, in any AI.
Add Idiolect AI to Claude, ChatGPT, or your coding agent once. From then on, when it writes for you, it writes as you — and can check the result against your own writing before you send it.
Add it to your AI.
Idiolect AI is one URL. Paste it into your AI’s connector settings and sign in — nothing to install, no key to manage.
https://idiolect.app/api/mcpWhere that goes, app by app:
Chat apps
Settings → Connectors → Add custom connector. Paste the URL, then sign in. Works on web, desktop, and mobile.
Custom connectors are in beta, and Claude's Free plan allows one.
Settings → Connectors → Advanced → turn on Developer mode. Then add a connector with the URL and sign in.
ChatGPT keeps custom connectors behind Developer Mode for now, so the free tier can't add one yet. One-click install lands with our directory listing.
Coding agents
One command, then sign in from inside Claude Code.
claude mcp add --transport http idiolect https://idiolect.app/api/mcp/mcpPick idiolect → Authenticate in the panel that opens. Add --scope user to use it in every project.
Or let Claude Code set itself up
Add the Idiolect AI MCP server for me: run `claude mcp add --transport http idiolect https://idiolect.app/api/mcp`, then tell me to run /mcp and choose Authenticate.One command — nothing to clone. Grab a key from Settings → API keys first.
codex mcp add idiolect \
--env IDIOLECT_API_KEY=your-key-here \
--env IDIOLECT_BASE=https://idiolect.app \
-- npx -y idiolect-mcpThat writes an [mcp_servers.idiolect] entry to ~/.codex/config.toml with your key — no shell export needed.
Or let Codex set itself up
Set up the Idiolect AI MCP server in Codex: run `codex mcp add idiolect --env IDIOLECT_API_KEY=<paste my key> --env IDIOLECT_BASE=https://idiolect.app -- npx -y idiolect-mcp`, then confirm it's registered.Using something else? Any client that supports remote MCP servers can use the same URL.
Nothing new to learn — just ask for writing the way you already would. Your AI reaches for Idiolect AI on its own.
- “Reply to this email in my voice.”
- “Score this LinkedIn post against how I actually write.”
- “Rewrite this paragraph so it sounds like me, and tell me whether it got closer.”
- “Draft a newsletter intro from these notes, in my voice.”
What it can do.
Loading your voice and scoring against it are free. Writing in your voice — rewrite_in_voice and draft_in_voice — needs Pro.
| Tool | Input | Plan |
|---|---|---|
| get_my_voice | none | Free |
| score_voice | text — 1–8,000 characters | Free |
| rewrite_in_voice | text — 1–8,000 characters | Pro |
| draft_in_voice | brief — 1–4,000 characters; format — linkedin | x_post | x_thread | newsletter | generic (optional) | Pro |
Your Voice Card plus the structured profile behind it — tone, signature moves, rhythm, and the things you’d never write. Called once, before your AI writes.
What the model sees
Use this when you are about to write anything on the user's behalf — emails, posts, messages, commit messages, PR descriptions, docs. Loads the user's Idiolect AI voice so you write as them.
Voice Match is relative: how much closer a draft reads to you than to generic model prose. Not a detector, and not forensic.
What the model sees
Check how close candidate prose is to the selected voice. Returns Voice Match only when the saved corpus and candidate are eligible; otherwise returns an unmeasured reason and safe evidence provenance.
If the rewrite scores worse than what you wrote, it keeps yours and says so, rather than handing back something flatter.
What the model sees
Rewrite supplied prose in the selected voice. Returns the safe recommendation plus the generated candidate and diagnostic delta; when the candidate regresses, the recommendation retains the original.
Writes from a brief in your voice. It matches how you write — never invents what you think.
What the model sees
Draft new prose in the selected voice from a supplied brief. Returns a Voice Match only when the saved corpus and draft are eligible, with explicit metric provenance.
What comes back
Scores arrive with their own provenance, so a client can always tell a real measurement from an unmeasured one — and never present an estimate as more than it is.
{
"voiceMatch": 84,
"measured": true,
"validated": true,
"instrument": "LUAR-MUD authorship embedding (validated)",
"register": "reddit-casual",
"approximate": true,
"reason": null,
"evidence": { "scoringEligible": true, "blockCount": 9, "characterCount": 4210 }
}relativeThe delta is the robust signal; register names the corpus the absolute anchors were fit on, and approximate stays true while they are. Full method and limits: Voice Match.
Building on this directly? The connector speaks Streamable HTTP and authenticates with OAuth 2.1; the same endpoint also accepts a personal API key as a bearer token. There’s a REST Score API too.
If something’s off.
It asks you to sign in again
The connection expired or was never completed. Remove the connector, add it again, and finish the sign-in. In ChatGPT, check Developer Mode is still on — switching it off drops the connection.
“No voice saved on this account yet”
You’re signed in, but this account has no voice yet. Make one at idiolect.app/onboard — and check you signed into the connector with the same account.
Rewrite or draft says you don’t have access
Those two are Pro. Loading your voice and scoring keep working on the free plan.
“Rate limit reached”
Writing and scoring are capped at 30 calls every 5 minutes. It clears on its own.
You get the writing, but no Voice Match
There isn’t enough of your writing saved yet to score against — roughly 600 characters across four separate pieces. You still get the draft; we’d rather withhold the number than show one that doesn’t mean anything. Add more samples in your Voice Profile.
Your AI never uses it
Check the connector is switched on for that conversation, then ask for the writing directly — “reply to this in my voice.” Some apps only pick up a new connector in a fresh chat.
Still stuck?
Email us. Tell us which app you connected from and roughly when it happened — that’s enough for us to find it. A person answers.
support@idiolect.app →What we do with your writing is set out in the privacy policy.