Skip to content

MCP server

E-commerce MCP Gateway

Local Java/Spring MCP server that looks up order status in an embedded database and uses a local Ollama model plus policy documents to suggest order issue resolutions.

  • Community
  • Runs locally
  • No credentials

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

ecommerceguide summary

A local MCP server, written in Java with Spring, that answers order issue queries. Its single tool, resolve_order, takes a five digit order ID, looks the order up in an embedded H2 database seeded at startup with five sample orders, matches a policy text for that status and asks a local Ollama model (phi3 plus nomic-embed-text) for a suggested resolution. It runs from source with Maven on localhost:8080 and exposes SSE and JSON-RPC endpoints.

Why it stands out

Runs inference only against a local Ollama instance, with no credentials or external API calls in its documented setup.

What E-commerce MCP Gateway does

ecommerceguide editorial
  • One tool, resolve_order, reads order status by five digit ID
  • Requires Java 21, Maven 3.9+ and a local Ollama instance
  • MCP endpoints: POST /mcp/sse stream and POST /mcp/message JSON-RPC
  • Started with mvn spring-boot:run; no Docker image or package
  • Swagger UI and OpenAPI JSON served at localhost:8080
  • Read only against seeded H2 data; no credentials or auth
  • Community project by vishalbhatt001; no licence file in the repository

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 support tooling who wants order lookups handled on their own machine

    Testing an MCP client against order status responses before wiring in a real order system

    Intended outcomeresolve_order returns the seeded order's status, the matching policy text and a resolution drafted by the local phi3 model.

  2. An engineer evaluating local models for post-purchase support questions

    Comparing responses from an on-machine model rather than a hosted API

    Intended outcomeThe server throttles inference to one request at a time and returns JSON-RPC error objects when the circuit breaker trips.

Who it suits

ecommerceguide editorial

Best for

You want a Java and Spring MCP server you can run locally with Ollama and adapt to your own order data.

Probably not for

You need a hosted endpoint, authentication, a licence file, write access or order data from a real store rather than seeded H2 records.

Business size
Any stageA source-only local server with no pricing or stated audience, so no scale band follows from the evidence.

Technical details

From the vendor's own pages

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

What an agent can do
Orders, Customer service
Transport
SSE (deprecated), HTTP (remote)
Authentication
No credentialsNo credentials shown; prerequisites are Java 21, Maven, and a local Ollama instance.
Package
None published; build from source
Language
Java
Repository last updated
17 Mar 2026

Connect E-commerce MCP Gateway

Third-party data
Install command
mvn spring-boot:run

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