Draft posts in Claude, create them in WordPress with status draft through the REST API, use Kinsta’s API for staging when you test theme or plugin changes, and publish yourself after review.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For drafting a checked WordPress article.
Drafting alternatives do not replace Kinsta, WordPress permissions or publishing. Choose one for drafting from approved material; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Source reconciliation comes before extra automation. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Keep the approved source pack and accepted output outside chat. Upload access is not publication permission.
Reviewed 2026-10-21. This page applies a shared comparison for “drafting from approved material” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
You preview the draft in WordPress and publish after review; approve staging-to-live changes separately.
Watch out for
Keep the human approval step: You preview the draft in WordPress and publish after review; approve staging-to-live changes separately.
Starter prompt
Goal: Keep WordPress publishing fast without skipping review. Tools involved: Claude, Kinsta. I will preview the draft, then publish. Work step by step, show me each draft or proposed change, and wait for my approval before anything is sent, published, signed, filed or changed in a live system.
Assembled from this page’s goal and steps. Paste it into your AI platform and adjust it to your situation.
WordPress REST API: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Kinsta: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
WordPress REST API: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Kinsta: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
WordPress REST API: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Kinsta: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
WordPress REST API: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Kinsta: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
Gemini
To verify
WordPress REST API: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Kinsta: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
WordPress REST API: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Kinsta: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked (2026-10-17)
WordPress REST API. A post’s status can be publish, future, draft, pending or private. Creating it with status draft keeps it off the site until you publish. Application Passwords (built in since WordPress 5.6) let a script authenticate without your main password.
Kinsta API is in public beta. Company owners, administrators and developers can create API keys, and a key’s access matches its creator’s role. The API can create a staging site, push staging to live, delete staging, clear the site cache and list sites and environments. Kinsta’s blog documents building a custom MCP server over the API; this does not establish a managed hosted MCP service.
Pricing. The reviewed US Single 20GB WordPress plan is $350 annually or $35 on monthly billing, before tax; check current promotions and usage allowances.
Set it up
Use a dedicated user with only the required capabilities and an Application Password over HTTPS. Author and Editor roles can publish; use a suitable restricted role if the integration must be technically unable to publish.
Have Claude draft the post, then send it to the posts endpoint with status draft.
Preview it in WordPress and fix formatting and links.
Publish yourself. Use Kinsta staging for theme or plugin changes rather than for individual posts. A staging push can overwrite live data, so approve it separately and check the operation result.
Keep credentials outside prompts and source code. Creating a draft is an external write even though it is unpublished. This proposed workflow has not created a post or tested the full handoff.