WooCommerce MCP Server

Created By
Vostos007a year ago
Model Context Protocol server for WooCommerce management
Overview

What is WooCommerce MCP Server?

WooCommerce MCP Server is a Model Context Protocol server designed for integrating WooCommerce stores with AI assistants and task management systems like Task Master.

How to use WooCommerce MCP Server?

To use the WooCommerce MCP Server, clone the repository, install dependencies, set up environment variables, and start the server using npm or Docker.

Key features of WooCommerce MCP Server?

  • Full integration with WooCommerce REST API v3
  • Bidirectional data synchronization between WooCommerce and Task Master
  • Compatibility with MCP 1.0 for AI assistants
  • Management of products, orders, customers, and analytics
  • Support for WordPress content (articles, SEO)
  • Webhook processing for reactive synchronization
  • Advanced utilities for caching, retries, and validation

Use cases of WooCommerce MCP Server?

  1. Integrating WooCommerce with AI-driven customer support systems.
  2. Automating task management for e-commerce operations.
  3. Enhancing product management and analytics through AI.

FAQ from WooCommerce MCP Server?

  • What are the requirements to run WooCommerce MCP Server?

Node.js 16.x or higher and WooCommerce 3.5+ with REST API v3 are required.

  • Is there support for Docker?

Yes, you can run the server using Docker for easier deployment.

  • How can I troubleshoot connection issues with WooCommerce API?

Ensure the store URL is correct, the API key has sufficient permissions, and the WooCommerce API is enabled.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Vostos007
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago