SellerSprite MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SELLERSPRITE_CDP_URL | No | 已登录 Chrome 的调试地址 | http://127.0.0.1:9222 |
| SELLERSPRITE_BROWSER_PATH | No | 可选；覆盖自动识别的 Chromium 浏览器程序 | |
| SELLERSPRITE_BROWSER_PROFILE | No | 可选；覆盖当前系统的登录浏览器持久化目录 | |
| SELLERSPRITE_CALL_TIMEOUT_MS | No | 单次调用超时毫秒数 | 120000 |
| SELLERSPRITE_MAX_OUTPUT_BYTES | No | 单次响应最大字节数 | 20971520 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sellersprite_list_operationsB | List available SellerSprite logged-in web and extension operations with their purpose and endpoint. |
| sellersprite_describe_operationB | Explain one operation: purpose, Agent input, actual logged-in web request, defaults, response, prerequisites, and verification. |
| sellersprite_callB | Execute a SellerSprite logged-in web or extension operation using the documented MCP tool input. |
| sellersprite_session_statusA | Check the attached Chrome SellerSprite web and extension login state without exposing credentials. |
| sellersprite_loginB | Open SellerSprite in the local default Chromium browser and wait for the user to complete sign-in. Credentials stay in the browser. |
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 5 tools
Each tool serves a distinct purpose: listing operations, describing one, executing one, checking session, and logging in. There is no overlap or ambiguity.
All tools use the 'sellersprite_' prefix, but the verb-noun pattern is not perfectly consistent: 'sellersprite_call' and 'sellersprite_login' lack a noun component, while others include one. Still, the naming is predictable and readable.
With 5 tools, the server is well-scoped for its purpose of managing SellerSprite operations. Each tool is necessary and none are redundant.
The tool set covers the full lifecycle of interacting with SellerSprite operations: login, list operations, describe an operation, execute it, and check session status. No obvious gaps for the intended domain.