Korea E-commerce Integrated Channel MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| channel_capabilitiesA | Show installed connectors, configuration state, and supported operations. |
| profile_listA | List local payload profiles that can turn one master product into channel bodies. |
| profile_previewA | Render a reviewed profile without calling any external seller API. |
| channel_healthB | Report configuration and connector-supported checks; inspect network_checked. |
| product_publishA | Preview or create one master product across all selected channels in parallel. |
| product_updateA | Preview or update a mapped product across selected channels in parallel. |
| product_stopC | Preview or stop a product on every selected channel. |
| product_resumeB | Preview or resume a product on every selected channel. |
| product_deleteB | Preview or permanently delete a mapped product across selected channels. |
| product_getA | Read the canonical product and its per-channel external identifiers. |
| operation_getA | Read a persisted operation, including per-channel partial failures. |
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 11 tools
Each tool targets a distinct resource and action: product lifecycle verbs (publish, update, stop, resume, delete, get), profile operations (list, preview), and channel introspection (capabilities, health). No two tools appear to perform the same function, so an agent can easily select the correct one.
The naming pattern is mostly consistent: product_<verb> for product operations, profile_<verb> for profile operations, and channel_<noun> for channel metadata. The only minor deviation is channel_capabilities and channel_health using nouns while others use verbs, but the pattern remains predictable and readable.
With 11 tools, the set is well-scoped for an e-commerce channel integration server. Each tool addresses a clear need without unnecessary bloat, covering product management, profile handling, and channel introspection in a balanced way.
The tool surface covers the full product lifecycle across channels: publish, update, stop, resume, delete, and get, plus profile management and operation status tracking. There are no obvious dead ends; all core workflows are supported, and the included channel capabilities/health tools round out the domain.