WordPress + WooCommerce MCP

For this integration, I turned selected WordPress and WooCommerce REST operations into local Model Context Protocol tools. Data-changing methods stay behind an explicit environment flag so write capability never feels accidental.

Abstract MCP bus connecting content and commerce operations through an explicit write gate

Problem

My goal was to explore content and commerce APIs from an AI coding workflow while keeping each tool typed, each request boundary predictable, and every mutating operation easy to identify.

Constraints

I kept site-specific data out of the portfolio interface
I placed every write-capable operation behind an explicit policy boundary
I limited the integration to selected operations from the two official REST APIs
I kept content and commerce actions separate enough to review independently

Technical decisions

I mapped MCP tool definitions directly to official REST API operations
I used an environment-controlled flag to enable write methods deliberately
I combined focused convenience tools with generic request helpers
I chose local process transport for the integration

Evidence

I ran a syntax check and a self-test that registered fourteen tools
I route mutating methods through the environment-controlled write gate
I still need an independent runtime check of the write gate and credential handling

What I learned

The project reinforced my preference for write access that stays narrow, visible, and testable before an integration moves beyond exploration.