菜单
WordPress MCP wrapper. Activate for WordPress content ops via an MCP server when available; else falls back to the wordpress-rest curl path. Manages posts, pages, media, taxonomies, SEO meta.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/trungdo9/ClauKit --skill mcp-wordpress命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
WordPress REST API client — connect to a live WP site to publish/update posts & pages (draft→publish), upload media, manage categories/tags, write Yoast/RankMath SEO meta, and audit existing content. Use when pushing generated marketing content to WordPress or auditing live WP articles. Auth via Application Passwords (env vars only). Consumer/client skill (not for building WP plugin endpoints).
Conversion Rate Optimization — landing pages, signup flows, popups, A/B tests. 25-point framework.
End-to-end SEO article production pipeline — from keyword strategy to published post. Standardizes a 6-stage flow (research/strategy → competitor analysis + outline → section-by-section writing → on-page optimization → media → internal-link + publish) into a Claude-native workflow. Ported from an n8n production pipeline. Use to plan, write, optimize, and publish complete SEO articles (single or at scale), incl. WordPress. State tracked via a content pipeline table (Supabase or a local plan file).
基于 SOC 职业分类
正在显示 SKILL.md
| name | mcp-wordpress |
| description | WordPress MCP wrapper. Activate for WordPress content ops via an MCP server when available; else falls back to the wordpress-rest curl path. Manages posts, pages, media, taxonomies, SEO meta. |
| allowed-tools | Read, Bash, Write |
WordPress content ops via an MCP server. Bring your own server — this skill documents the tools + falls back to the
wordpress-restcurl path when no server is configured.
Server command: npx -y @automattic/wordpress-mcp (or a community equivalent — BYO server)
Required env: WP_SITE_URL, WP_USER, WP_APP_PASSWORD
Setup: WP Admin → Users → Profile → Application Passwords
| Tool | Purpose |
|---|---|
mcp__wordpress__createPost | Create post (status: draft|publish) |
mcp__wordpress__updatePost | Update post by id |
mcp__wordpress__listPosts | List/fetch posts (audit) |
mcp__wordpress__uploadMedia | Upload media, return id |
mcp__wordpress__getTaxonomies | List/create categories & tags |
mcp__wordpress__getSiteInfo | Discovery / connectivity |
(Exact tool names depend on the chosen server — adapt to its manifest. Use the mcp-manager agent to discover real tool names.)
Tool: mcp__wordpress__createPost
Args: { title, content, status: "draft", slug, categories: [...], tags: [...] }
DRAFT default — publish only on explicit user confirmation (echo target URL + title, get "yes").
Tool: mcp__wordpress__listPosts → fetch by id → hand to the `seo` skill (claude-seo).
| Error | Cause | Fix |
|---|---|---|
| auth failed / 401 | bad Application Password | regenerate Application Password, update env |
| 403 | user lacks publish_posts capability | grant role, or REST blocked by security plugin |
| tool not found | MCP server not configured | use Manual Fallback below |
If mcp__wordpress__* tools are unavailable → activate skills/integrations/wordpress-rest/ and use the curl path: preflight (GET /wp-json/) → idempotent upsert by slug → draft default. All endpoint/auth detail lives there (single source of truth — not duplicated here).
Same as wordpress-rest: env-only credentials, draft-default with explicit-publish confirmation, idempotent upsert. See wordpress-rest for enforcement detail.
skills/integrations/wordpress-rest/SKILL.md — REST client (the fallback + source of truth).claude/workflows/automation-rules.md — MCP + idempotency + PII rulesskills/automation/mcp-resend/SKILL.md — sibling MCP-wrapper pattern