WooCommerce MCP Server

Created By
techspawna year ago
A WooCommerce (MCP) Model Context Protocol server
Overview

What is WooCommerce MCP Server?

WooCommerce MCP Server is a Model Context Protocol (MCP) server designed for integrating with WooCommerce, allowing interaction with WooCommerce stores through the WordPress REST API.

How to use WooCommerce MCP Server?

To use the WooCommerce MCP Server, clone the repository, install the dependencies using npm install, and build the project with npm run build. Configure the server with your WooCommerce credentials in the MCP settings file.

Key features of WooCommerce MCP Server?

  • Supports both WordPress and WooCommerce API methods.
  • Allows management of products, orders, customers, shipping, taxes, and more.
  • Compatible with Windows, macOS, and Linux.

Use cases of WooCommerce MCP Server?

  1. Automating product management in WooCommerce stores.
  2. Integrating WooCommerce with other applications via API.
  3. Managing customer orders and shipping through a centralized server.

FAQ from WooCommerce MCP Server?

  • What are the requirements for using WooCommerce MCP Server?

You need Node.js 20.0.0 or higher and a WordPress site with the WooCommerce plugin installed.

  • Is there a license for WooCommerce MCP Server?

Yes, it is licensed under the MIT License.

  • How do I authenticate with the WooCommerce API?

You need to generate API keys in your WordPress dashboard under WooCommerce → Settings → Advanced → REST API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
techspawn
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago