Test your outreach in Claude Code.
Draft with your company context, catch weak spots with Quality Check, and simulate ICP reactions before you send. Documents and results stay in your Unpitch workspace.
What it does
Claude Code reads context, writes Documents, and spends only on evaluation.
Reads your context
The authorised workspace, bounded Knowledge Base excerpts with their sources, and the Personas you can simulate against.
Writes Documents
Creates and revises outreach Documents in your workspace. Every change is revision-checked, so it never overwrites newer work.
Spends only on evaluation
Runs Quality Check and Simulation on an exact Document revision, and asks you to confirm before any run that costs credits.
How it works
Three steps, then it is part of how you write.
- 01
Install with one command
One claude mcp add command registers Unpitch in Claude Code. It uses a public client and never asks for a secret.
- 02
Authorise one workspace
Run /mcp, sign in through your browser and choose the workspace Claude Code may use. The browser returns straight to Claude Code.
- 03
Work where the work lands
Documents and results appear in Unpitch as they are created. Settings shows which calls this connection made and lets you revoke it.
The complete command, the authorisation flow and what to do when something does not connect are on the setup guide.
Where the boundaries are
An agent that can move the ground under its own evaluation is not a tool you can trust.
Never writes your Knowledge Base or Personas
Claude Code cannot change the context every evaluation is scored against. The one thing it writes is a Document, which is the thing being judged.
One organisation-wide credit limit
Credits admitted through Claude Code count against a monthly limit shared by everyone in your organisation. Owners and admins set it in Settings.
Scoped to the workspace you chose
Reads are scoped to the authorised workspace. Internal identifiers, prompts and other workspaces are never exposed.
Claude Code is the supported client. Unpitch speaks the standard MCP transport with OAuth, so other clients may connect, but only the Claude Code path is tested and documented. Revoking access in Settings denies the next request from any client.
Ready when you are.
One command, one authorisation, and your next draft is tested before it leaves the editor.