Skip to content

MCP server

MCP Store

MCP server that queries a local store API to list customers, search customers by name, and retrieve a customer's orders.

  • Community
  • Runs locally
  • No credentials

Repository and documentation last checked Built from public product pages and documentation. SourcesClaim this listing

ecommerceguide summary

MCP Store is a community MCP server that queries a store API running locally on http://localhost:3000 and returns customer and order data to an MCP client such as Claude. Three read-only tools list all customers, search customers by name and fetch a customer's orders by ID. It runs locally over stdio with no authentication, installed by cloning the JavaScript repo, running npm install and npm run build.

Why it stands out

A community example server that reads from a store API on localhost:3000 rather than a hosted commerce platform.

What MCP Store does

ecommerceguide editorial
  • Three read tools: all customers, customer by name, orders by customer
  • Requires a local API server on http://localhost:3000 supplying the data
  • Runs locally over stdio, no credentials or API keys
  • Installed from source: git clone, npm install, npm run build
  • Built on @modelcontextprotocol/sdk with axios and zod, ISC licence
  • Maintained by community developer n0119566; last pushed March 2025
  • Read-only access, so no writes to customers or orders

How ecommerce teams could use it

ecommerceguide editorial

Illustrative scenarios written by ecommerceguide from the product's documented capabilities. They are not customer case studies.

  1. A developer building a store backend in Node with customer and order endpoints

    Wanting to query that data conversationally from Claude during development

    Intended outcomeMCP Store runs over stdio and exposes get-all-customers, get-customer-by-name and get-all-orders-by-customer against the local API.

  2. A team handling order queries against an in-house store API

    Looking up a shopper's order history by searching on their name

    Intended outcomeThe name search tool returns matching customers, then the orders tool returns that customer's orders by ID.

  3. A developer learning how MCP servers are structured

    Needing a small JavaScript server to read and adapt

    Intended outcomeThe repo ships source with an ISC licence, a build script and three documented read tools to extend.

Who it suits

ecommerceguide editorial

Best for

You run your own store API on localhost and want three read-only customer and order tools in an MCP client, installed from source.

Probably not for

You need writes, authentication, a hosted endpoint, or a connector to Shopify or another hosted commerce platform, since this reads only from a local API.

Business size
Any stageNo pricing or stated audience; the only requirement is Node.js and a local store API.

Technical details

From the vendor's own pages

From the server's repository, documentation and MCP directory listings.

What an agent can do
Orders, Customers
Transport
stdio (local)
Authentication
No credentialsPrerequisites list only Node.js and a local API server on http://localhost:3000; no credentials mentioned.
Package
mcp-store
Language
JavaScript
Repository last updated
31 Mar 2025

Connect MCP Store

Third-party data
Install command
git clone <repository-url> && cd mcp-store && npm install && npm run build

Command as listed on the repository README, not tested by ecommerceguide. Check the repository README (opens in a new tab) for configuration and credentials before running it.

Categories and use cases

Sources

ecommerceguide profiles are built from public product information and written for ecommerce teams. We do not test products, and paying never changes where a listing ranks.

Also listed on PulseMCP.

See something incorrect? Report an update