Using Handwrite with Claude and MCP | Handwrite Help Center

Handwrite can be used with Claude through MCP, which lets Claude create drafts, request previews, quote orders, and send postcards on your behalf.

The key thing to understand is that MCP is not a separate ordering system. It is a thin connection layer on top of the same Handwrite API.

What MCP means in practice

When you connect Claude to Handwrite through MCP:

Claude uses your Handwrite API access
the same company credit balance is used
the same order rules and safeguards apply
the same previews, quotes, and final orders are created underneath

So whether an order comes from your own code or from Claude through MCP, it still ends up in the same Handwrite order system.

What you can use it for

MCP is useful when you want Claude to help with tasks like:

preparing postcard drafts
checking available handwriting styles
previewing a recipient-specific proof
getting a quote before a send
placing a real order after approval

What MCP does not change

MCP does not bypass the core rules of the platform.

It does not:

create a separate balance
skip quote and send safeguards
avoid credit requirements
turn every conversation into a confirmed order automatically

That is intentional. The goal is to make the workflow easier, not less safe.

Recommended workflow with Claude

The best pattern is still:

ask Claude to create or refine the draft
preview a realistic recipient
request a quote
review the total and wording
confirm the send

This is the best balance between convenience and control.

Who should use MCP

MCP is a strong fit for teams that want a more conversational workflow on top of the Handwrite API, especially when they want help preparing message variants, checking drafts, or operating from an AI-enabled environment.

If you want a more traditional integration, you can also work directly against the Handwrite API without Claude.

API keys and setup

MCP uses Handwrite API access behind the scenes.

At the moment, API access is configured as part of a managed setup rather than a fully self-serve developer portal. If your team wants to connect Claude or another MCP-compatible client, contact Handwrite so the right access and billing setup can be enabled.

Credits still work the same way

MCP orders are paid from the same prepaid company credit balance used by the direct API.

That means:

previews do not spend credits
quotes do not spend credits
real sends do spend credits

If you want the cleanest mental model, think of MCP as a smart interface for the same order engine, not as a separate product.

For the safest ordering pattern, follow the draft, preview, quote, and send workflow. For billing questions, see how credits work for API orders.