القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need to plan technical solutions that are scalable, secure, and maintainable.
Conversion Rate Optimization — landing pages, signup flows, popups, A/B tests. 25-point framework.
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).
Multi-MCP marketing orchestrator. Activated by /mk:campaign and Phase 9 (Measure) of the marketing workflow. Coordinates across GA4, GSC, SendGrid/Resend, and ReviewWeb MCP wrappers for full-funnel campaign execution + measurement.
Google Analytics 4 MCP wrapper. Activate when user needs traffic reports, real-time data, attribution, or any GA4 metrics. Routes to MCP tools if available, else falls back to manual CSV export.
Google Search Console MCP wrapper. Activate for SEO analytics — search queries, indexing status, sitemaps, keyword rankings. Routes to MCP tools if available, else manual CSV export fallback.
| 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