vanam-erp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_API_TOKEN | Yes | 재고앱 내부 API 인증용 머신 토큰. 재고앱 .env의 MCP_API_TOKEN과 같은 값이어야 합니다. | |
| INVENTORY_API_BASE | No | 재고앱 내부 API 베이스 URL. 기본값 http://192.168.0.210:3000 | http://192.168.0.210:3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_itemsA | 재고 품목을 이름이나 코드로 검색한다. 예: 'VO2', '타겟'. 품목의 id, code, name, category를 반환한다. 재고 수량을 알려면 이 도구로 먼저 품목 id를 찾은 뒤 get_stock을 호출하라. |
| get_stockA | 특정 품목의 현재 재고 수량을 조회한다. 품목 id가 필요하다(search_items로 먼저 찾을 것). itemCode, itemName, currentQty를 반환한다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Each tool has a distinct purpose: search_items finds item IDs based on name/code, while get_stock retrieves stock quantity for a specific item. There is no functional overlap.
Both tools use a consistent verb_noun pattern (search_items, get_stock) with snake_case, making the naming predictable and clear.
With only 2 tools, the server feels undersized for an ERP system. While they form a minimal query workflow, a typical inventory toolset would include more operations.
The tools only cover searching items and querying stock levels. Missing CRUD operations for items and stock adjustments leave significant gaps for an inventory management server.