한국어

Work / Demo

MCP server for your shop back office

An MCP server that lets Claude and other AI agents search, check and update shop data through validated tools.

Role
Design and development
Stack
Node.jsTypeScriptMCPClaudezodVitest

Situation

AI agents become useful at work when they can read and change real business data. That access needs limits: validated inputs, safe writes and a record of every change.

What I built

  • Six tools: product search, product details, stock update, order list, order details and a low-stock report
  • Input validation on every tool, and stock changes that would go below zero are refused
  • An audit log entry for every stock change, with time, reason and the values before and after
  • A local stdio transport for Claude Desktop and Claude Code, and a remote HTTP transport with token auth
  • Data access behind one repository interface, so connecting a real REST API or database means writing one class

Result

36 automated tests check tool behavior, input validation and refused requests. The same structure fits order management, ERP or support systems that a team wants an agent to use.

The six tools the server exposes, with their input schemas
Six tools, each with a plain-language description and a typed input schema.
A stock change rejected and the audit log entry for an accepted change
Writes are checked before they run, and every accepted change goes into the audit log.
HTTP requests to the MCP endpoint with and without a token
The remote HTTP transport refuses requests without a valid token.

All work