Ordercore Mcp

ai.ordercorePublished by ordercore.aiv0.2.18Updated Oct 24, 2026

Commerce backend for AI agents: catalog, prices, inventory, orders, idempotent checkout.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server that gives an assistant a commerce backend: catalog, prices, inventory, orders and idempotent checkout.

What you can do
  • Browse the product catalog and look up prices and inventory levels.
  • Create and manage orders, including idempotent checkout so a retried request does not duplicate a purchase.
  • Run without a key against a read-only sandbox, or with a full key to perform checkout.
  • Point the server at a different API base URL if needed.
When to use it
Useful when an assistant needs to look up products, prices or stock, or place orders through an Ordercore commerce backend, and when you want to try it safely in a read-only sandbox first.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. No authentication is required for the read-only sandbox; checkout needs ORDERCORE_API_KEY, obtained from the provider's bootstrap page. ORDERCORE_BASE_URL optionally overrides the default API endpoint. Network access to the Ordercore API is required.
Before you install
Checkout with a full key can create real orders and may involve payment, so treat ORDERCORE_API_KEY as a sensitive credential and keep it out of shared configuration. The server sends catalog, order and checkout data to the Ordercore API at the configured base URL. Prefer the keyless read-only sandbox until you are confident in the workflow.

Installation

In SourceWeft

  1. Open Ordercore Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.18LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.