README.md

README.md

1. # Meridian Orders MCP
3. A read-only [Model Context Protocol](https://modelcontextprotocol.io) server
4. that lets Claude look up orders, customers, statuses and split shipments in
5. Meridian Display Co.'s order system, Plinth.
7. **The company is fictional.** This server was built for, and used at, a real
8. print and display shop. Here it serves **Meridian Display Co.**, the invented
9. company behind
10. [meridian-ops-board](https://github.com/mattrguerra/meridian-ops-board) and
11. [meridian-crm-mcp](https://github.com/mattrguerra/meridian-crm-mcp). Plinth,
12. its API, its endpoint, method and field names, and every number in its
13. reference are invented too; the engineering is the real server's.
15. ## What is worth reading
17. - **A write-prevention failsafe** (`mcp-server/src/lib/guard.ts`). The API is
18. one endpoint where a query parameter picks the action, so a read and a write
19. differ by one string. Four independent layers make a write impossible to
20. dispatch, even through the passthrough tools or from plain JavaScript.
21. - **A shared rate limiter** (`mcp-server/src/lib/rateLimit.ts`,
22. `mcp-server/src/rateLimiterDO.ts`). The API allows 10 requests per 10
23. seconds across everyone. A pure scheduling function paces requests rather than
24. failing them, backed by one Durable Object on Workers so the budget holds
25. across every session.
26. - **Two runtimes, one core.** The same tools run over stdio for local use and
27. over HTTP on Cloudflare Workers for a shared, hosted server.
28. - **A live-request gate.** Nothing reaches production until
29. `PLINTH_ALLOW_LIVE_REQUESTS=true` and a key are both set.
31. ## Layout
33. ```
34. mcp-server/ the server (see its README)
35. docs/PLINTH-API.md the API reference the server is written against
36. ```
38. ## Setup
40. There is no `package.json` at the repo root; the server manages its own
41. dependencies.
43. ```
44. cd mcp-server
45. npm install
46. npm run dev # local stdio server
47. ```