mcpField
W
wordpress-mcp-dev

wordpress-mcp-dev

github.com/respira-pressDevelopment4996 installsUpdated 1w ago
Repository

About wordpress-mcp-dev

WordPress + MCP Development is an agent skill for building WordPress plugins, MCP servers, or hybrid projects. It provides an implementation workflow, security guardrails, and release checklists focused on delivering a validated vertical slice.

Key features

  1. 01Plugin, server, and hybrid planning
  2. 02Vertical-slice implementation workflow
  3. 03Security and validation guardrails
  4. 04MCP tool contract guidance
  5. 05Lifecycle and release checklists

Use cases

  1. 01Scaffolding a WordPress plugin
  2. 02Building an MCP server with read and write tools
  3. 03Connecting a plugin endpoint to an MCP tool

MCP support

The skill covers MCP server architecture, transport, tooling, and tool schema design. It guides development of servers that expose tools to MCP clients.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/respira-press/agent-skills-wordpress --skill wordpress-mcp-dev

After installing, type/wordpress-mcp-devin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/full-guide.md

Details

From the project README

WordPress + MCP Development

Use this skill to ship production-grade WordPress plugins, MCP servers, or both together.

Workflow

  1. Identify target product shape: plugin, mcp-server, or hybrid.
  2. Choose architecture and scaffold from the relevant reference.
  3. Implement minimum viable vertical slice first:
    • Plugin: one secure REST route + one real feature path.
    • MCP: one read-only tool + one mutating tool with safe validation.
    • Hybrid: one plugin endpoint consumed by one MCP tool.
  4. Add safety controls before expanding scope: capability checks, nonce/auth, sanitized errors, and rollback strategy.
  5. Validate against checklists before release.

Guardrails

  • Keep plugin bootstrap thin; place behavior in namespaced classes.
  • Prefix all plugin symbols to avoid collisions.
  • Treat MCP tool schemas/descriptions as API contracts for model behavior.
  • Return actionable errors and avoid leaking secrets.
  • Prefer duplicate-first content edits for AI-assisted write operations.

References

  • Core guide: references/full-guide.md
  • WordPress plugin architecture and security sections: references/full-guide.md
  • MCP server design, transport, and tooling sections: references/full-guide.md
  • Lifecycle, testing, and distribution checklists: references/full-guide.md

Comments

Markdown supported