Pancake POS MCP

Pancake POS teams ask AI to inspect orders and manage stock transfers to coordinate sales and warehouse work.

Best for: Pancake POS teams using AI assistants

Visit website

Overview

Pancake POS MCP connects assistants to the Pancake POS REST API. It brings orders, inventory and customer operations into a configurable local or hosted MCP service.

Who it suits

Merchants using Pancake POS who have a shop API key and want assistant access to orders, products, customers, warehouses, and supported purchasing workflows.

Who it may not suit

Businesses that only have Pancake social-inbox credentials, or teams looking for a connector to an unrelated point-of-sale system.

Seller use cases

  • Read and manage POS orders, products and customers.
  • Work with warehouses, purchases and stock transfers.
  • Inspect supported promotions and multichannel commerce operations.

What you can do

  • Read and manage POS orders, products and customers.
  • Work with warehouses, purchases and stock transfers.
  • Inspect supported promotions and multichannel commerce operations.

What you need

  • Bun, a Pancake POS API key and shop ID; social-inbox credentials are different.

Install

Local stdio

git clone https://github.com/nguyennguyenit/pancake-pos-mcp.git
cd pancake-pos-mcp
bun install
cp .env.example .env
# Configure PANCAKE_POS_API_KEY and PANCAKE_POS_SHOP_ID before starting.
bun run src/index.ts
Installation source ↗

Permissions & data

The Bun process reads configuration and calls pos.pages.fm. HTTP or Workers deployment exposes those account operations behind the configured bearer token.

Project info

Maintainer
nguyennguyenit
GitHub stars at check date
32
Last commit
2026-10-08
License
MIT
Last checked
2026-10-30
GitHub ↗

Pricing at a glance

Free

Pricing

The repository provides a Bun-based connector with local and hosted deployment options. Pancake POS access, runtime hosting, and AI-client usage must be provisioned independently; the code does not supply a POS account.

Limitations

The configured shop ID determines the operating scope, and supported tools can change POS data.

Alternatives to Pancake POS MCP

Frequently asked questions

The README distinguishes Pancake POS credentials from social-inbox credentials. Configure the POS API key and shop ID required by this connector.

The documented local setup uses Bun. HTTP and Workers deployment are additional options with their own service-access configuration.

Access still follows the configured POS credentials and shop scope. Hosting changes how clients reach the server, not which seller account has authorized the underlying operations.

Checked against the official site on 2026-10-30 · Official source ↗

Sources