MGC_MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MGC_STOCK_API_URL | No | Custom stock API URL to use instead of the default menu API. | |
| MGC_APP_USER_AGENT | No | User-Agent header for API requests. Default: okhttp/4.12.0 | |
| MGC_APP_API_BASE_URL | No | Base URL for the Mega Coffee app API. Default: https://app.annhouse.co.kr/api/ | |
| MGC_STORE_CACHE_PATH | No | Path to the store cache JSON file. Default: data/mgc-stores.json |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| refresh_mgc_storesB | Fetch all Mega MGC Coffee app stores and save them to the local JSON cache. |
| list_mgc_stores_by_regionB | List stores from the local cache by region. Refreshes cache automatically if missing or expired. |
| find_mgc_storesB | Find Mega MGC Coffee stores by latitude/longitude or Korean sigungu name. |
| search_mgc_menuB | Search public Mega MGC Coffee menu pages by Korean or English menu text. |
| check_mgc_stockB | Check stock for a Mega MGC Coffee menu item. Without MGC_STOCK_API_URL this returns public-site evidence with unknown stock status. |
| check_mgc_stock_nationwideB | Check Mega MGC Coffee app API sold_out values across stores nationwide or filtered by region. Use itemCode for exact lookup when known. |
| check_mgc_stock_by_regionA | Check Mega MGC Coffee app API sold_out values only for stores matching a region query. Example: 서울 종로구 or 서울 종로구 이화동 혜화동. |
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 7 tools
Most tools have distinct purposes: stock checking split by scope (public site vs app, regional vs nationwide) and store listing split by search method (lat/lng vs region from cache). However, 'check_mgc_stock' and 'check_mgc_stock_by_region' could be confused if users don't read descriptions carefully, and 'find_mgc_stores' vs 'list_mgc_stores_by_region' have overlapping outputs.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., 'check_mgc_stock', 'find_mgc_stores', 'search_mgc_menu'). The naming is predictable and easy to understand.
With 7 tools, the set is well-scoped for the domain of checking stock and finding stores for a coffee chain. Each tool serves a clear purpose without unnecessary duplication.
The tool set covers core operations: stock checking via multiple methods, store finding, menu search, and cache refresh. Minor gaps exist, such as no tool to retrieve store details (hours, address) or update stock, but these are not essential for a read-only consumer service.