connectors: add WordPress + WooCommerce adapters#231
Merged
Conversation
WordPress (39 tools) and WooCommerce (50 tools) adapters as declarative
JSON manifests. Both use BASIC_AUTH — WP App Passwords / WC consumer
key+secret over HTTPS.
Tool families per connector:
- CRUD primitives covering posts/pages/users/media/comments for WP and
products/variations/orders/customers/coupons/reports for WC
- 9 enum-helper static tools (Pipedream-style reference cards for
status / role / period / test-slug values)
- 11 skill static tools — multi-step workflow playbooks delivered
on-demand via method:"static" + staticResponse, not preloaded into
the connector instructions block
Move static-method support to first-class for REST adapters by adding
STATIC to VALID_REST_METHODS in catalog.spec.ts — the runtime
(ConnectorsService and DynamicMcpTools) already intercepts
method:"static" + staticResponse before engine dispatch.
All tools live-tested end-to-end against a docker-compose WordPress 6.8
+ WooCommerce stack with seeded data (7 products, 3 orders, 1 customer,
1 coupon): 92/92 pass.
keysersoft
force-pushed
the
keysersoft/wp-woo-connectors
branch
from
e1a9650 to
f5d0a64
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two new connectors landing as declarative JSON manifests under
packages/backend/src/adapters/intl/. Zero platform code changes.BASIC_AUTHvia WP Application Passwords, hits/wp-json/wp/v2. Covers posts, pages, taxonomies, media, users, comments, search, site-health, settings, plus post-meta for Yoast/Rank Math SEO.BASIC_AUTHvia REST consumer key+secret, hits/wp-json/wc/v3. Covers products + variations, orders + notes + refunds, customers, coupons, reports.Both connectors require HTTPS in production (documented in
instructions).New tool families (pattern)
wordpress_list_site_health_test_slugs,woocommerce_list_order_status_options) — reference cards delivered on-demand viamethod:"static". Pattern inspired by Pipedream'slist-*-optionsactions.wordpress_skill_seo_content_pipeline,woocommerce_skill_inventory_optimization) — multi-step workflow playbooks that the agent reads only when actually running that workflow, instead of preloading them into the always-oninstructionsblock.Platform alignment
STATICadded toVALID_REST_METHODSincatalog.spec.ts. The runtime (ConnectorsService+DynamicMcpTools) was already interceptingmethod:"static"+staticResponsebefore engine dispatch — the test gate was the only thing blocking the pattern for REST adapters.Test plan
catalog.spec.ts— 450/450 pass (was 426; +24 for the new tools)tsc --noEmitclean