Test publishing without touching a live site
Docswrite has no separate sandbox host. Instead, every publish can be a draft, a Docswrite hosted blog can stand in for the real site, and the discovery MCP server needs no account.
5 free exports. No credit card required.
Six ways to test
API base URL https://api.docswrite.com. Product MCP https://api.docswrite.com/mcp.
Publish as a draft
POST /api/v1/posts and the MCP tool publish_post draft by default (status "draft"): the post lands in the destination unpublished, so you can check formatting, images and SEO fields before anything goes live.
curl -s -X POST https://api.docswrite.com/api/v1/posts \
-H "Authorization: Bearer $DOCSWRITE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"connection_ids": [123], "title": "Test", "content": "Hello", "status": "draft"}'Use a Docswrite hosted blog as a test destination
A Docswrite hosted blog is a destination with no CMS to run. Point your agent at its connection id while you build, then switch the id to the real site.
Call the no-auth MCP server
The discovery MCP server answers without an account: list destinations, read pricing and the auth guide, and check your MCP client end to end before the OAuth sign-in.
curl -s -X POST https://docswrite.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Retry safely
Send an Idempotency-Key with every publish. Re-running the same request replays the first response for 24 hours instead of publishing twice.
Send a test webhook
The Test button on each webhook endpoint sends a signed webhook.test event, so you can verify your signature check before real events arrive.
Free exports
A free workspace includes 5 exports with no credit card, enough to run the whole flow against your own site.
Authentication, scopes and errors: Docswrite API authentication. Everything else: Docswrite developer portal.