Sellfox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SELLFOX_CLIENT_ID | Yes | 赛狐 OpenAPI client_id | |
| SELLFOX_CLIENT_SECRET | Yes | 赛狐 OpenAPI client_secret | |
| SELLFOX_CREDENTIAL_DB | No | 多账号凭据池数据库路径（可选） | |
| SELLFOX_BOOTSTRAP_TOKEN | Yes | 管理员 Token，首次启动时设置，用于创建 API Key |
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
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 70 tools
Most ad tools are clearly separated by campaign type and entity, but several tools have overlapping or nearly identical purposes, such as sellfox_store_sales vs sellfox_product_sales and sellfox_online_products vs sellfox_online_products_v2. The old/new version pairs and multiple profit/settlement dimension tools leave unclear boundaries that agents will struggle to resolve reliably.
All tools follow a consistent sellfox_ prefixed snake_case convention, and the SP/SB/SD entity pattern is highly predictable. Minor deviations like sellfox_ads_aba_search_term lacking a report suffix, and health_check/smoke_check being operational rather than data-oriented names, prevent a perfect score.
With 70 tools, this server is far beyond the reasonable size for a coherent MCP toolset, making selection expensive and overwhelming. The broad domain does not justify the sheer number, especially when several tools are legacy/duplicate variants.
The server covers the major read-only reporting domains well: products, orders, ads, inventory, FBA shipments, returns, profits, settlements, and reviews. Some gaps exist, such as order-detail lookup and campaign management actions, but for a reporting-focused ERP data server the coverage is strong.