Receber por email
← Voltar para o catálogo

wordpress-mcp-dev

Build and maintain modern WordPress plugins and MCP servers, including hybrid WordPress+MCP products. Use when implementing plugin architecture (PHP, REST API, Gutenberg/admin/page-builder integrations), MCP tooling (TypeScript/Python, stdio/HTTP transport), security hardening, licensing/updates, and delivery workflows from scaffold to distribution.

34estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add respira-press/agent-skills-wordpress

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/wordpress-mcp-dev/svg)](https://www.skillteca.com.br/skills/wordpress-mcp-dev)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  4. Plugin: one secure REST route + one real feature path.
  5. MCP: one read-only tool + one mutating tool with safe validation.
  6. Hybrid: one plugin endpoint consumed by one MCP tool.
  7. Add safety controls before expanding scope: capability checks, nonce/auth, sanitized errors, and rollback strategy.
  8. 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
Compartilhar X LinkedIn