StatusPro MCP server
Commit 13 Nov 2026Memungkinkan asisten AI untuk membaca dan memperbarui status pesanan, mengelola tenggat waktu, serta menambahkan komentar riwayat melalui StatusPro API.
Juga dikenal sebagai dougborg/statuspro-openapi-client
- Stars
- 0
- Tools
- 10
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 13 Nov 2026
- Lisensi
- MIT
Apa itu StatusPro MCP?
Memungkinkan asisten AI untuk membaca dan memperbarui status pesanan, mengelola tenggat waktu, serta menambahkan komentar riwayat melalui StatusPro API. Server ini menyediakan 10 tool, seperti list_orders, get_order, lookup_order.
Ringkasan dibuat dari README proyek
Tentang StatusPro MCP server
MCP server ini memungkinkan merchant yang menggunakan StatusPro API untuk mengelola progres produksi pesanan dan pembaruan pelanggan. Dengan menghubungkannya ke asisten AI seperti Claude Desktop atau Cursor, Anda dapat berinteraksi dengan data pesanan melalui bahasa alami. Server ini menyediakan jembatan untuk membaca detail pesanan, memeriksa transisi status yang valid, dan memperbarui informasi pesanan langsung dari antarmuka chat.
Untuk menggunakan server ini, Anda harus menyediakan STATUSPRO_API_KEY melalui environment variables pada konfigurasi client Anda. Server ini menyertakan tool khusus untuk berbagai tugas, seperti list_orders, lookup_order, dan update_order_status. Demi keamanan, setiap tool mutasi seperti add_order_comment atau bulk_update_order_status menggunakan pola konfirmasi dua langkah yang memerlukan persetujuan eksplisit dari Anda sebelum perubahan diterapkan ke API. Hal ini memastikan asisten AI tidak dapat secara tidak sengaja mengubah status pesanan atau tenggat waktu tanpa izin Anda.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Tool StatusPro MCP 10
Terdeteksi dari READMElist_ordersget_orderlookup_orderlist_statusesget_viable_statusesupdate_order_statusadd_order_commentupdate_order_due_datebulk_update_order_statusstatuspro
| list_orders | — | |
| get_order | — | |
| lookup_order | — | |
| list_statuses | — | |
| get_viable_statuses | — | |
| update_order_status | — | |
| add_order_comment | — | |
| update_order_due_date | — | |
| bulk_update_order_status | — | |
| statuspro | — |
Konfigurasi
STATUSPRO_API_KEYSTATUSPRO_BASE_URL
| Nama | Deskripsi | Tipe |
|---|---|---|
| STATUSPRO_API_KEY | — | |
| STATUSPRO_BASE_URL | — |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaudougborg/statuspro-openapi-client is public and reachablegithub.com/dougborg/statuspro-openapi-client ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-13github.com/dougborg/statuspro-openapi-client ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubStatusPro — API Client Ecosystem
Multi-language client ecosystem for the StatusPro API, a small REST API for reading and updating the status of orders. The StatusPro API is used by merchants to expose production progress to their customers (order received → in production → shipped, etc.) and to update that status from their own systems.
This monorepo ships:
- A production-grade Python client with transport-layer retries, rate-limit awareness, and auto-pagination across all list endpoints.
- A TypeScript client generated from the same OpenAPI spec.
- An MCP server exposing StatusPro operations as tools to AI assistants like Claude Desktop.
Packages
| Package | Language | Version | Description |
|---|---|---|---|
| statuspro-openapi-client | Python | 0.1.0 | API client with transport-layer resilience |
| statuspro-mcp-server | Python | 0.1.0 | Model Context Protocol server for AI assistants |
| statuspro-client | TypeScript | 0.1.0 | TypeScript/JavaScript client with full type safety |
Features
| Feature | Python | TypeScript | MCP Server |
|---|---|---|---|
| Automatic retries (network + 5xx) | Yes | Yes | Yes (via Python client) |
| Rate-limit retry with exponential backoff | Yes | Yes | Yes |
| Auto-pagination (page + per_page with meta) | Yes | Yes | Yes |
| Two-step confirm on mutations | — | — | Yes |
| Full type safety (attrs + Pydantic / TS) | Yes | Yes | Yes |
| AI tool surface | — | — | Claude, Cursor, etc. |
Quick Start
Python Client
pip install statuspro-openapi-client
import asyncio
from statuspro_public_api_client import StatusProClient
async def main():
async with StatusProClient() as client:
orders = await client.orders.list(per_page=25)
for order in orders:
status = order.status.name if order.status else "(no status)"
print(f"{order.name}: {status}")
asyncio.run(main())
TypeScript Client
npm install statuspro-client
import { StatusProClient } from "statuspro-client";
const client = await StatusProClient.create();
const response = await client.get("/orders");
const { data, meta } = await response.json();
console.log(`Found ${meta.total} orders (page ${meta.current_page}/${meta.last_page})`);
MCP Server (Claude Desktop)
pip install statuspro-mcp-server
Add to Claude Desktop config
(~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"statuspro": {
"command": "uvx",
"args": ["statuspro-mcp-server"],
"env": {
"STATUSPRO_API_KEY": "your-api-key-here"
}
}
}
}
Configuration
All packages authenticate via bearer token:
- Environment variable:
STATUSPRO_API_KEY .envfile:STATUSPRO_API_KEY=your-key- Direct parameter: pass
api_key=...to the client constructor ~/.netrc:machine app.orderstatuspro.com+password your-key
# .env
STATUSPRO_API_KEY=your-api-key-here
STATUSPRO_BASE_URL=https://app.orderstatuspro.com/api/v1 # optional override
API Coverage
The StatusPro API is intentionally small and focused on order status. All 7 endpoints are covered:
| Tag | Method | Path | Purpose |
|---|---|---|---|
| Orders | GET | /orders |
Paginated list with filters (search, status, tags, due date). |
| Orders | GET | /orders/{id} |
Full detail for one order including history. |
| Orders | GET | /orders/lookup |
Look up an order by order number + customer email. |
| Orders | GET | /orders/{id}/viable-statuses |
Statuses that are valid transitions from the current state. |
| Orders | POST | /orders/{id}/status |
Change the status of a single order. |
| Orders | POST | /orders/{id}/comment |
Add a history comment (5/min rate limit). |
| Orders | POST | /orders/{id}/due-date |
Set or update the due date (single date or range). |
| Orders | POST | /orders/bulk-status |
Update up to 50 orders at once (5/min, queued asynchronously). |
| Statuses | GET | /statuses |
Every status defined on the account (code, name, color). |
Conventions:
- Bearer token auth on every endpoint (
Authorization: Bearer <STATUSPRO_API_KEY>). GET /ordersreturns{"data": [...], "meta": {current_page, last_page, per_page, total, from, to}}.GET /statusesandGET /orders/{id}/viable-statusesreturn raw JSON arrays.- Pagination uses
page+per_pagequery params (per_pagemax 100). - Rate limits are documented per-endpoint (60/min on most, 5/min on
/commentand/bulk-status) but not surfaced in response headers.
MCP Tools
The statuspro-mcp-server package maps each endpoint to a tool. Mutations use a
two-step confirm pattern: call with confirm=false for a preview, then confirm=true
to apply (the client elicits explicit user approval).
| Tool | Mutation? | Description |
|---|---|---|
list_orders |
no | Filter + paginate orders |
get_order |
no | Full detail for one order |
lookup_order |
no | Find an order by number + customer email |
list_statuses |
no | Full status catalog |
get_viable_statuses |
no | Valid transitions for an order |
update_order_status |
yes | Change one order's status |
add_order_comment |
yes | Add a history comment |
update_order_due_date |
yes | Set or change the due date |
bulk_update_order_status |
yes | Change status for up to 50 orders at once |
Plus two resources:
statuspro://statuses— JSON list of every status (cached read).statuspro://help— tool reference and recommended workflows.
Resilience (Python client)
Every endpoint inherits these transport-layer behaviors automatically — no decorators or wrappers needed:
- Retries:
httpx-retriesretries idempotent methods on 502/503/504 and any method on 429. Configurable viamax_retries. - Rate-limit awareness:
Retry-Afterheaders are honored when present; otherwise exponential backoff. - Auto-pagination:
GET /ordersis walked to completion usingmeta.last_pageas the stop condition, up tomax_pages(default 100) or an explicitmax_itemsoverride. Raw-array endpoints (/statuses,/viable-statuses) are never paginated. - Sensitive-data redaction: Authorization headers and common secret field names
(
api_key,password,email, etc.) are scrubbed from log output.
Project Structure
statuspro-openapi-client/ # Monorepo root
├── pyproject.toml # Workspace configuration (uv)
├── uv.lock # Python lock file
├── pnpm-workspace.yaml # TS workspace
├── docs/
│ ├── statuspro-openapi.yaml # OpenAPI 3.1.0 spec (source of truth)
│ └── *.md # Shared documentation
├── statuspro_public_api_client/ # Python client
│ ├── statuspro_client.py # Resilient client + transport layer
│ ├── domain/ # Hand-written Pydantic domain models
│ ├── helpers/ # Ergonomic facades (client.orders, .statuses)
│ ├── utils.py # unwrap/unwrap_as/unwrap_data + error types
│ ├── api/, models/ # Generated from the OpenAPI spec
│ └── docs/ # Package documentation
├── statuspro_mcp_server/ # MCP server
│ └── src/statuspro_mcp/
│ ├── server.py # FastMCP server
│ ├── tools/ # 9 tools (orders + statuses)
│ └── resources/ # help + statuses resources
└── packages/
└── statuspro-client/ # TypeScript client
├── src/
│ └── generated/ # Generated from the same spec
└── openapi-ts.config.ts
Development
Prerequisites
Setup
git clone https://github.com/dougborg/statuspro-openapi-client.git
cd statuspro-openapi-client
uv sync --all-extras # install Python deps
uv run pre-commit install # install git hooks
pnpm install # install TS deps
cp .env.example .env # add STATUSPRO_API_KEY
Common Commands
uv run poe quick-check # fast: format + lint
uv run poe check # full: format + lint + typecheck + test
uv run poe test # just tests (pytest -n 4)
uv run poe regenerate-client # regenerate the Python client from docs/statuspro-openapi.yaml
uv run poe generate-pydantic # regenerate Pydantic v2 models
pnpm --filter statuspro-client generate # regenerate the TypeScript client
Commit Standards
Conventional commits drive per-package release-please versioning. Which package(s) get bumped is decided by which paths a commit touches, not its scope — but scopes remain useful for changelog readability:
git commit -m "feat(client): add helper for archived orders"
git commit -m "fix(client): handle empty viable-status responses"
git commit -m "feat(mcp): add tool for lookup by date range"
git commit -m "feat(ts): export pagination helpers"
git commit -m "docs: update quick-start"
Use ! for breaking changes: feat(client)!: drop Python 3.11 support.
See RELEASE.md for details.
License
MIT License — see LICENSE.
Contributing
Contributions welcome. See CONTRIBUTING.md for guidelines.
Pertanyaan tentang StatusPro MCP
Tool apa yang disediakan StatusPro MCP?
Server ini menyediakan 10 tool, termasuk list_orders, get_order, lookup_order, list_statuses, get_viable_statuses.
Apa yang bisa saya lakukan dengan StatusPro MCP server ini?
Anda dapat melihat daftar, mencari, dan mendapatkan detail pesanan, melihat status yang tersedia, memperbarui status pesanan, menambahkan komentar, serta mengelola tenggat waktu.
Apakah server ini mendukung pembaruan massal?
Ya, Anda dapat memperbarui status untuk hingga 50 pesanan sekaligus menggunakan tool bulk_update_order_status.