Coupang MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Coupang MCP Serversearch for iPhone 15 case"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Coupang MCP Server
MCP (Model Context Protocol) 서버로 Claude AI가 쿠팡 제휴 API를 사용하여 상품 검색 및 정보 조회를 할 수 있도록 합니다.
기능
상품 검색: 키워드로 쿠팡 상품 검색
상품 상세 조회: 상품 ID로 상세 정보 확인
카테고리별 베스트 상품: 카테고리별 인기 상품 조회 (18개 카테고리 지원)
딥링크 생성: 쿠팡 URL을 트래킹 코드가 포함된 단축 URL로 변환
제휴 링크 제공: 쿠팡 파트너스 제휴 링크 생성
비동기 처리: aiohttp를 사용한 효율적인 API 호출
Related MCP server: Shopee Agentic MCP Server
요구사항
Python 3.13+
UV (Python 패키지 관리자)
쿠팡 파트너스 API 자격증명
설치
방법 1: PyPI 패키지 설치 (권장) ⭐
가장 간단한 방법입니다. 한 줄로 설치하고 Claude Desktop에서 바로 사용할 수 있습니다.
pip install mcp-coupang-server**📦 PyPI 설치 가이드**를 참조하세요.
이 가이드는 다음 내용을 포함합니다:
PyPI 패키지 설치 방법
Claude Desktop 설정 (환경 변수 포함)
문제 해결 및 업데이트 방법
방법 2: Git Clone (개발자용)
소스 코드를 직접 수정하거나 기여하고 싶다면 이 방법을 사용하세요.
# 1. 저장소 클론
git clone https://github.com/space-cap/mcp-coupang-server.git
cd mcp-coupang-server
# 2. 의존성 설치
uv sync
# 3. 환경 변수 설정
# .env 파일을 생성하고 쿠팡 API 키를 입력하세요**📖 Git Clone 설치 가이드**를 참조하세요.
이 가이드는 다음 내용을 포함합니다:
Python 및 UV 설치 방법
쿠팡 파트너스 API 키 발급 절차
Claude Desktop 설정 방법 (Windows/macOS/Linux)
문제 해결 및 테스트 방법
환경 변수
.env 파일 예제:
COUPANG_ACCESS_KEY=your_access_key_here
COUPANG_SECRET_KEY=your_secret_key_here
COUPANG_PARTNER_ID=your_partner_id_here
COUPANG_SUB_ID=your_sub_id_here # Optional: Default tracking ID for deeplinks사용 방법
로컬 테스트
MCP 서버를 직접 실행:
uv run python main.pyClaude Desktop과 연동
Claude Desktop 설정 파일(claude_desktop_config.json)에 다음을 추가:
Windows:
{
"mcpServers": {
"coupang": {
"command": "uv",
"args": [
"--directory",
"C:\\path\\to\\mcp-coupang-server",
"run",
"python",
"main.py"
]
}
}
}macOS/Linux:
{
"mcpServers": {
"coupang": {
"command": "uv",
"args": [
"--directory",
"/path/to/mcp-coupang-server",
"run",
"python",
"main.py"
]
}
}
}자세한 설정 방법은 docs/claude-desktop-setup.md를 참조하세요.
제공되는 도구
1. search_products
키워드로 쿠팡 상품을 검색합니다.
매개변수:
keyword(string, 필수): 검색어 (예: "laptop", "iPhone 15")limit(integer, 선택): 결과 개수 (1-100, 기본값: 10)
예제:
검색어 "노트북"으로 상품 20개 검색응답:
Found 20 product(s) for '노트북':
1. LG 그램 17인치 노트북
Price: 1,899,000원
ID: 1234567890
🚀 Rocket Delivery
📦 Free Shipping
URL: https://link.coupang.com/...
2. 삼성 갤럭시북 Pro
Price: 1,499,000원
...2. get_product_details
상품 ID로 상세 정보를 조회합니다.
매개변수:
product_id(string, 필수): 쿠팡 상품 ID
예제:
상품 ID "1234567890"의 상세 정보 조회응답:
Product Details for ID: 1234567890
Name: LG 그램 17인치 노트북
Price: 1,899,000원
Original Price: 2,299,000원
Discount: 17% (Save 400,000원)
Category: Electronics
Shipping: 🚀 Rocket Delivery, 📦 Free Shipping
Image: https://thumbnail.coupangcdn.com/...
Affiliate URL: https://link.coupang.com/...3. get_best_products_by_category
특정 카테고리의 베스트 상품을 조회합니다.
매개변수:
category_id(string, 필수): 쿠팡 카테고리 IDlimit(integer, 선택): 결과 개수 (1-100, 기본값: 20)
사용 가능한 카테고리:
1001- 여성패션1002- 남성패션1010- 뷰티1012- 식품1013- 주방용품1014- 생활용품1015- 홈인테리어1016- 가전디지털1017- 스포츠/레저1018- 자동차용품1019- 도서/음반/DVD1020- 완구/취미1021- 문구/오피스1024- 헬스/건강식품1025- 국내여행1026- 해외여행1029- 반려동물용품1030- 유아동패션
예제:
가전디지털 카테고리(1016)의 베스트 상품 10개 조회응답:
Found 10 best product(s) in category '1016':
1. 삼성전자 갤럭시 버즈3 Pro
Price: 289,000원
ID: 8123456789
Category: 가전디지털
🚀 Rocket Delivery
📦 Free Shipping
💰 Discount: 10%
URL: https://link.coupang.com/...
2. LG전자 그램 스타일 노트북
Price: 1,790,000원
...4. create_deeplinks
쿠팡 상품 URL을 트래킹 코드가 포함된 단축 URL로 변환합니다.
매개변수:
coupang_urls(array, 필수): 변환할 쿠팡 URL 목록sub_id(string, 선택): 트래킹/Sub ID (환경 변수 기본값 사용 가능)
예제:
다음 쿠팡 URL을 딥링크로 변환해줘:
https://www.coupang.com/vp/products/184614775응답:
Created 1 deeplink(s):
1. Original: https://www.coupang.com/vp/products/184614775
Shortened: https://coupa.ng/blE0dT
Landing: https://link.coupang.com/re/AFFSDP?lptag=AF1234567&pageKey=319834306&itemId=1023216541&vendorItemId=70064597513&traceid=V0-183-5fddb21eaffbb2ef활용 사례:
검색 결과에서 얻은 상품 URL을 추적 가능한 링크로 변환
여러 상품의 URL을 한 번에 변환하여 링크 관리
Sub ID를 사용하여 다양한 트래픽 소스 추적
프로젝트 구조
mcp-coupang-server/
├── src/
│ ├── __init__.py
│ ├── server.py # MCP 서버 메인 로직
│ ├── coupang_client.py # 쿠팡 API 클라이언트
│ ├── models/
│ │ ├── __init__.py
│ │ └── product.py # 상품 데이터 모델
│ ├── tools/
│ │ ├── __init__.py
│ │ ├── search.py # 검색 도구 유틸리티
│ │ └── details.py # 상세정보 도구 유틸리티
│ └── utils/
│ ├── __init__.py
│ ├── config.py # 환경 변수 관리
│ ├── auth.py # HMAC 인증
│ └── categories.py # 카테고리 코드 정의
├── playground/ # 테스트 스크립트 (콘솔)
│ ├── 1_simple_search.py
│ ├── 2_product_details.py
│ ├── 3_compare_products.py
│ ├── 4_price_filter.py
│ ├── 5_rocket_delivery.py
│ ├── 6_category_best.py
│ ├── 7_create_deeplinks.py
│ └── README.md
├── tests/ # 테스트 파일
├── docs/ # 문서
├── main.py # 진입점
├── pyproject.toml # 프로젝트 설정
└── pytest.ini # 테스트 설정배포
다른 사람들이 사용할 수 있도록 배포하고 싶으신가요? **🚀 배포 가이드**를 참조하세요.
배포 방법:
GitHub 공개 저장소 (가장 쉬움, 권장)
PyPI 패키지 배포
Docker 컨테이너
MCP Registry 등록
개발
테스트 실행
# 모든 테스트 실행
uv run pytest
# 상세 출력과 함께 실행
uv run pytest -v
# 특정 테스트 파일만 실행
uv run pytest tests/test_client.py
# 커버리지와 함께 실행 (pytest-cov 설치 필요)
uv run pytest --cov=src --cov-report=html코드 품질
프로젝트는 다음을 준수합니다:
Type hints 사용
Pydantic을 통한 데이터 검증
비동기 프로그래밍 (asyncio/aiohttp)
포괄적인 단위 테스트 및 통합 테스트
라이선스
이 프로젝트는 MIT 라이선스 하에 배포됩니다. 자세한 내용은 LICENSE 파일을 참조하세요.
MIT License - Copyright (c) 2025 space-cap기여하기
기여를 환영합니다! CONTRIBUTING.md를 참조하세요.
문제 보고
버그를 발견하거나 기능 요청이 있으시면 이슈를 생성해주세요.
관련 링크
참고사항
이 서비스는 쿠팡 파트너스 활동의 일환으로, 이에 따른 일정액의 수수료를 제공받습니다
Available Tools
3 toolscreate_deeplinksA
Convert Coupang product URLs to affiliate tracking deeplinks. Takes regular Coupang URLs and converts them to shortened tracking URLs with your affiliate code. Useful for creating trackable links from search results or specific product pages.
| Name | Required | Description | Default |
|---|---|---|---|
| coupang_urls | Yes | List of Coupang product URLs to convert (e.g., ['https://www.coupang.com/vp/products/184614775']) | |
| sub_id | No | Optional tracking/sub ID for analytics (uses environment default if not provided) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries burden. It explains conversion to shortened tracking URLs with affiliate code, but omits details like rate limits, error handling, or whether URLs must be valid Coupang links.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with action, no redundancy. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers purpose and parameter usage sufficiently for a simple tool with no output schema. Could mention output format but overall adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage 100%, so baseline 3. Description adds that sub_id uses environment default if not provided, slight extra value beyond schema fields.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it converts Coupang URLs to affiliate tracking deeplinks. Specific verb+resource, and distinguishes from sibling tools which search or get products.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says it's useful for creating trackable links from search results or specific product pages, giving clear context. No exclusions stated, but enough guidance for typical use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_best_products_by_categoryA
Get best-selling products in a specific Coupang category. Returns a list of top products in the category with names, prices, and affiliate URLs. Useful for finding popular items in specific categories.
Available categories: 1001-여성패션, 1002-남성패션, 1010-뷰티, 1012-식품, 1013-주방용품, 1014-생활용품, 1015-홈인테리어, 1016-가전디지털, 1017-스포츠/레저, 1018-자동차용품, 1019-도서/음반/DVD, 1020-완구/취미, 1021-문구/오피스, 1024-헬스/건강식품, 1025-국내여행, 1026-해외여행, 1029-반려동물용품, 1030-유아동패션
| Name | Required | Description | Default |
|---|---|---|---|
| category_id | Yes | Coupang category ID (e.g., '1016' for 가전디지털) | |
| limit | No | Maximum number of results to return (1-100, default: 20) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits beyond the read nature (e.g., rate limits, authentication, or side effects). The description is minimal in this dimension.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the purpose in the first sentence. The category list is lengthy but necessary for usability. It is well-structured and earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (2 params, simple return), the description covers purpose, parameter hints, and mentions return fields (names, prices, affiliate URLs). No output schema exists, so the description is adequately complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline 3. The description adds value by listing all available category IDs and their Korean names, which is more informative than the schema's single example.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get best-selling products' and the resource 'specific Coupang category', and distinguishes itself from siblings like 'search_products' by focusing on best-sellers within a category.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says it's 'useful for finding popular items in specific categories', implying when to use. However, it does not explicitly contrast with siblings or state when not to use, but the category list provides concrete context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_productsA
Search for products on Coupang by keyword. Returns a list of products with names, prices, images, and affiliate URLs. Useful for finding products, comparing prices, or discovering items.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | Search query keyword (e.g., 'laptop', 'iPhone 15', 'coffee maker') | |
| limit | No | Maximum number of results to return (1-100, default: 10) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It describes basic behavior (search by keyword, return list with details) but omits potential behavioral traits such as authentication requirements, pagination behavior, rate limits, or whether the search is exact or fuzzy. The mention of 'affiliate URLs' is useful but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main action ('Search for products on Coupang by keyword') and followed by concise details on return data and use cases. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately covers return fields and the keyword-based search. It also provides usage scenarios. However, it could mention pagination behavior or potential limitations (e.g., search accuracy). The sibling tools are related, but no cross-references are made.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for both parameters (keyword and limit), so the schema already fully documents them. The description adds value by describing return fields (names, prices, images, affiliate URLs) but does not add meaning to the parameters beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as searching for products on Coupang by keyword, and it distinguishes itself from siblings like 'get_best_products_by_category' (category-based) and 'create_deeplinks' (link creation). It specifies the action (search) and resource (products) with a clear platform context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says 'Useful for finding products, comparing prices, or discovering items,' which implies general usage scenarios but does not explicitly state when to avoid this tool or when to use a sibling tool instead. No exclusions or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
v1.0.0- First observed
create_deeplinks - First observed
get_best_products_by_category - First observed
search_products
TDQS
Scored across 3 tools
Each tool has a distinct purpose: creating affiliate links, browsing best products by category, and searching products. No overlap.
All tool names follow a consistent verb_noun snake_case pattern (create_deeplinks, get_best_products_by_category, search_products).
3 tools is appropriate for a focused affiliate link server; covers core operations without being too many or too few.
Covers creating links, browsing categories, and searching. Minor gap: no direct product detail lookup beyond search results, but sufficient for affiliate use cases.
Maintenance
Related MCP Connectors
AI-powered product search, affiliate links, and price negotiation for e-commerce platforms
Turn product links or queries into tracked links that can earn. Carts and search too.
Public K-beauty catalog, product search, and latest-offers tools with canonical product facts.
Create geo-targeted affiliate smart links, pull analytics, and rewrite YouTube descriptions.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables affiliate marketing and product promotion across Taobao, JD.com, and Pinduoduo platforms with link conversion, product search, and order tracking capabilities.352 npm120ISC
- FlicenseNot gradedqualityDmaintenanceConnects AI agents to the Shopee platform for real-time product searches and category mapping via the Affiliate and Seller Center APIs. It enables users to filter products by keyword, category, and commission rates directly through natural language.1-
- AlicenseNot gradedqualityCmaintenanceEnables searching Coupang products and checking real-time lowest prices via Claude Desktop, with rocket delivery distinction and price formatting.17MIT
- FlicenseAqualityDmaintenanceEnables searching, price comparison, trend analysis, and saving of Korean e-commerce products (Naver Shopping) using natural language.4-