Compatible with every major AI agent and IDE
What is the WordPress Post Drafter MCP Server?
We refused to build a bloated WordPress integration that gives an AI agent terrifying access to delete your pages, read your entire database, or install plugins. Instead, this MCP server provides a surgical, zero-trust bridge: just creating Drafts.
Your AI agent gains the immediate ability to act as a ghostwriter. You can brainstorm ideas, ask it to write a 2,000-word SEO-optimized blog post, and then just say "Save it to my blog". It instantly appears in your WordPress panel, ready for your human review.
The Superpowers
- Zero-Friction Publishing: End the 'copy-paste' nightmare. The AI formats the HTML and drops it right into your CMS.
- Zero-Bloat Integration: No custom plugins required. It uses the native WordPress REST API
/wp-json/wp/v2/posts. You only need an Application Password (a native WordPress feature). - Absolute Containment: Because the code is strictly hardcoded to
status: 'draft', the agent is physically incapable of publishing content live to your audience. You maintain 100% editorial control. It is a completely secure, one-way funnel.
Built-in capabilities (1)
Provide the title and the content (can be HTML or plain text). The post will strictly be saved as a Draft, never published live. Creates a new Draft post in WordPress with the provided content
Why Claude Code?
Claude Code registers WordPress Post Drafter as an MCP server in a single terminal command. Once connected, Claude Code discovers all 1 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where WordPress Post Drafter data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using WordPress Post Drafter tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
WordPress Post Drafter in Claude Code
WordPress Post Drafter and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect WordPress Post Drafter to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for WordPress Post Drafter in Claude Code
The WordPress Post Drafter MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
WordPress Post Drafter for Claude Code
Every tool call from Claude Code to the WordPress Post Drafter MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the AI publish the post directly without my approval?
No! This is the most important feature. The MCP code has a hardcoded status: 'draft' payload. Even if the AI tries to publish it, the server will force it into a Draft. You must click 'Publish' in your WordPress admin panel.
Do I need to install a plugin on my WordPress?
No. We use the official, native WordPress REST API. You only need to generate an Application Password, which is a built-in feature in WordPress since version 5.6.
How do I add an MCP server to Claude Code?
Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
Explore More MCP Servers
View all →
Make (Workflow Automation)
7 toolsManage workflow automation via Make — audit scenarios, track execution logs, and monitor data stores.

Xiaomi Push Service / 小米推送
6 toolsXiaomi's essential device push platform — send notifications to MIUI and Global devices via AI.

Parsio
12 toolsExtract structured data from emails and PDFs automatically with AI-powered parsing templates that learn from your documents.

Cron Expression Calculator
1 toolsCalculate the exact future dates of any Cron expression using deterministic JavaScript. Stop LLMs from failing date mathematics and leap year edge cases.
