KoreanSkinpedia MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KSP_API_KEY | No | API 키 (Authorization: Bearer). API가 API_KEY 설정 시 필요. | |
| KSP_API_URL | Yes | 발행 API 베이스 URL (필수) |
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 |
|---|---|
| create_articleA | KoreanSkinpedia 아티클 발행(API 호출). 의료 필수: reviewer{name,cred}, sources[{n,label,url?}](최소 1), medicallyReviewedAt(ISO). 필드: title, lang(en/ko/zh/ja), tag(skincare/procedures/trends), excerpt, read(분), tldr[], related[], translateNote?, body(마크다운). 발행 즉시 사이트에 반영. |
| create_procedureB | 시술 가이드 발행(API). 의료 필수 동일. 필드: name, lang, tagline, priceRange, duration, recovery, definition, how[{n,text}], goodFor[], tldr[], faqs[{q,a}], clinicsHere[], body(마크다운). |
| upsert_clinicB | 클리닉 생성/수정(API). 필드: name, area, verified, rating?, reviewCount?, procedures[], priceList[{name,time,price}], from, langs[], hours, address, payment[], about, reviews[]. |
| healthA | 발행 API 상태 확인(store 모드, 버킷). |
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 4 tools
Each tool has a clearly distinct purpose: article creation, procedure guide creation, health check, and clinic upsert. No overlap in functionality.
Two tools use 'create_' prefix, one uses 'upsert_', and one uses a noun 'health'. While mostly consistent, the 'health' tool breaks the verb_noun pattern slightly.
With 4 tools, the set is well-scoped for a specialized content management server. Each tool serves a distinct, necessary function without bloat.
The set covers creation and upsert for articles, procedures, and clinics, but lacks retrieval (get/list) or deletion tools. Agents may need to query existing data, which is unsupported.