Skip to content
ecommerceguide.
Explore ecommerceguide.

MCP servers with Windsurf setup.

14 MCP servers whose documentation includes setup steps for Windsurf. Counts servers whose own documentation gives setup steps for that client. A server without them may still work with any client that supports its transport.

MCP servers
14
run locally
12
offer a hosted endpoint
3
Repositories and docs last checked
Sept 2026

Active filters

2 MCP servers match your filters

Showing 1 to 2 of 2, ordered by recently updated

How results are ordered

By the date the server's source repository last changed, newest first. Hosted servers without a public repository use the date we last read their documentation. This is a measure of recent activity, not quality.

There are no paid placements in the MCP directory, and no ratings.

  1. WordPress DevDocs

    Community

    by pluginslab (Marcel Schmitz)

    Local MCP server that indexes WordPress, WooCommerce, Gutenberg and custom plugin hooks, APIs and handbooks into SQLite so AI coding tools can search and validate them.

    • WooCommerce logoWooCommerce
    • WordPress logoWordPress

    Tasks: Store development

    Runs
    Local · stdio
    Auth
    No credentials
    Setup for
    Claude Code, Cursor, Windsurf
    Install
    npm
    GitHub (opens in a new tab)View profile for WordPress DevDocs

  2. WP-AGENT MCP Server

    Community

    by soyeb-salar

    Local MCP server giving AI coding assistants a WordPress/WooCommerce knowledge base, code checklists, PHP analysis and live site data read via WP-CLI.

    • WooCommerce logoWooCommerce
    • WordPress logoWordPress

    Tasks: Manage products · Orders · Store development · Product content

    Runs
    Local · stdio
    Auth
    No credentials
    Setup for
    Claude Desktop, Cursor, Windsurf
    Install
    Source only
    GitHub (opens in a new tab)View profile for WP-AGENT MCP Server

From the ecommerceguide dataset

MCP servers with Windsurf setup in numbers

Calculated from all 14 servers on this page's list. Each figure opens the list filtered to it.

MCP servers listed
14
Published by the connected platform
4 29%
Can run locally
12 86%
Offer a hosted endpoint
3 21%
Ask for an API key
10 71%
Support OAuth sign-in
4 29%

Most listings by integration

A count of listings, not of usage.

What an agent can do

Transport

Authentication

Where a server's documentation lists its tools, 10 can create or change data and 4 only read it. The other 0 do not list their tools clearly enough to say.

What to check before connecting an MCP server

An MCP server acts with the access you give it to your store, payments or marketing accounts.

  1. What it can access

    Check which tools it exposes and whether any create, change or delete data, issue refunds or send messages. Profiles record read-only or read and write only where the documentation lists the tools.

  2. Where it runs

    A local server runs on your machine with the credentials you give it. A hosted server runs on the maintainer's infrastructure, so your requests pass through it.

    Hosted servers

  3. How it authenticates

    Local servers usually read an API key or access token from a config file. Hosted servers can use OAuth, where you sign in to the platform and approve the access requested.

    Servers with OAuth

  4. Who maintains it

    Official servers come from the platform's own company. A community server is not endorsed by the platform it connects to, even when its name suggests otherwise.

    4 official servers

  5. Whether your client supports it

    Clients differ in which transports they support. Check the transport a server uses against your client's documentation before installing.

  6. How active it is

    Each profile shows when the source repository last changed. Archived repositories are not listed here.

Understand MCP and agentic commerce

How this directory works

Where listings come from

Candidates are found on public MCP directories (PulseMCP, mcpservers.org, MCP Market, Build with Claude), on vendor sites, and through submissions. A directory listing is only a lead; nothing is listed from it alone.

How each one is checked

We read the source repository through the GitHub API (README, file tree, package manifests, licence, archive status), the npm package where one is named, the official MCP Registry, and the vendor's documentation for hosted servers. Last full check: Sept 2026.

What gets listed

Only MCP servers, or plugins that install one, that connect to a commerce platform, perform store operations, or serve a business function ecommerce teams use (SEO, ads, analytics, support, accounting). Duplicates are merged into one listing.

What “official” means

Published by the company whose product the server connects to, from that company's GitHub organisation or own domain. Anything else is labelled third-party company or community.

What is extracted, and how

Integrations, tasks, transport, authentication and the clients a server documents setup for are extracted by a language model from that evidence, with the evidence kept for review. Commands are shown as documented and are not tested by us.

What is not listed

Of 219 candidates reviewed, 48 were plugins, skills or libraries without an MCP server, 45 were not about running a store, 11 were duplicates and 17 had an archived, missing or unverifiable source.

Corrections: hello@ecommerceguide.com.