OHMS
Exposes Shopify order and inventory management tools via MCP, allowing agents to fetch, update, and print orders without exposing raw Shopify credentials.
README
OHMS - Order Hub Management System
Flauraly Flowers and Plants - Python FastMCP server hosted on Replit Reserved VM.
Purpose
OHMS exposes a small, hardened set of order- and inventory-related tools to Violet (and any other authorized MCP client) over the Model Context Protocol. It centralizes Shopify Admin REST access behind a Bearer-auth gate so agents never touch raw Shopify credentials.
Architecture
+-----------------+ Bearer +------------------------------+
| MCP Client | ---------------> | OHMS (Replit Reserved VM) |
| (Violet, etc.) | /mcp or /sse | |
+-----------------+ | Starlette parent app |
| +-- /health (open) |
| +-- /mcp (Streamable HTTP)|
| +-- /sse (SSE fallback) |
| +-- BearerAuthMiddleware |
+--------------+---------------+
|
v
+------------------------------+
| Shopify Admin REST API |
+------------------------------+
Both /mcp (Streamable HTTP) and /sse (Server-Sent Events fallback) are
mounted simultaneously so any MCP client transport profile works.
Environment Variables
OHMS authenticates to Shopify via the OAuth 2.0 client_credentials grant.
The server never holds a long-lived SHOPIFY_ACCESS_TOKEN; instead it holds a
SHOPIFY_CLIENT_ID + SHOPIFY_CLIENT_SECRET pair and mints a short-lived
access token on demand against https://{shop}.myshopify.com/admin/oauth/access_token.
The minted token is cached in-memory with a 5-minute clock-skew buffer and
re-minted automatically (or on a 401/403 from any subsequent call). All values
are read via os.environ.get(...). Nothing is hardcoded.
| Var | Purpose |
|---|---|
PORT |
TCP port to bind (Replit injects this; defaults to 8080). |
OHMS_API_TOKEN |
Static bearer token required on every non-/health request (client to OHMS auth - separate from Shopify). |
SHOPIFY_STORE_URL |
Shop domain, e.g. flauraly.myshopify.com. |
SHOPIFY_CLIENT_ID |
Shopify app client ID (used for OAuth client_credentials grant). |
SHOPIFY_CLIENT_SECRET |
Shopify app client secret (used for OAuth client_credentials grant). Rotate per Secrets_Registry.md schedule. |
SHOPIFY_API_VERSION |
Pinned Shopify API version, e.g. 2025-01. |
PRINTER_IP |
Local network IP of the receipt printer (stub uses this). |
See .env.example for the placeholder template.
Local Dev (Windows)
OHMS reads .env only when running locally (via python-dotenv). Bootstrap
your .env from the Windows DPAPI-protected secrets store rather than typing
secrets in plaintext:
# 1. Pull each secret from DPAPI into the local .env (PowerShell pseudocode)
$secrets = @("OHMS_API_TOKEN","SHOPIFY_STORE_URL","SHOPIFY_CLIENT_ID","SHOPIFY_CLIENT_SECRET","SHOPIFY_API_VERSION","PRINTER_IP")
foreach ($k in $secrets) {
$v = Unprotect-DpapiSecret -Name $k # your local helper
Add-Content .env "$k=$v"
}
# 2. Run the server
python -m venv .venv
.venv\Scripts\Activate.ps1
pip install -r requirements.txt
python main.py
The server listens on http://0.0.0.0:8080 by default. Probe with:
curl http://localhost:8080/health
# => OHMS OK
Replit Deploy
- Create a Replit project and import this folder.
- In the Secrets pane, set every variable from
.env.example(using the real values - never paste them into any committed file). - Confirm
.replitshowsdeploymentTarget = "reserved_vm"and port8080 -> 80. - Deploy. The public URL is
https://ohms-server.crashzero9.replit.app. - Verify both transports:
curl https://ohms-server.crashzero9.replit.app/health curl -H "Authorization: Bearer $OHMS_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","method":"tools/list","id":1}' \ https://ohms-server.crashzero9.replit.app/mcp
Tool Registry
| Tool | Source | Notes |
|---|---|---|
get_order(order_id) |
Shopify Admin REST | GET /orders/{id}.json |
list_pending_orders() |
Shopify Admin REST | GET /orders.json?status=open&limit=50 |
update_order_status(order_id, status) |
Shopify Admin REST | PUT /orders/{id}.json (sets tags) |
get_inventory_snapshot() |
Shopify Admin REST | GET /inventory_levels.json?limit=50 |
get_doordash_orders_via_browser() |
Stub | Returns routing dict for browser-automation handoff. |
print_order_ticket(order_id) |
Stub | Reads PRINTER_IP; returns queued status. Driver pending. |
Phase Status
- Phase 1 (current): MVP scaffold, Bearer auth, six tools (4 live + 2 stubs), Replit Reserved VM deploy, basic pytest suite.
- Phase 2 (planned): OAuth 2.1 replacing static bearer, full DoorDash driver, real network printer driver, structured logging with secret redaction, rate limiting.
Security Notes
- No secret values appear in any committed file.
Authorizationheaders and full Shopify response bodies are never logged./healthreturns only the literal stringOHMS OK- no version, env, or path info.- All
httpxcalls have an explicit 30-second timeout.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。