alibaba-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.
alibaba-mcp connects this agent to the user's Chrome tab at https://message.alibaba.com/. The Alibaba session stays in Chrome. Do not ask for cookies, passwords, or session tokens. Call alibaba_status first. Access is exactly one of none, read, or read/write. The extension enforces it. The default is read-only. Read and send by conversation id through the open messenger page. The open chat does not have to change. Get the user's explicit approval before sending. Show the exact conversation and the exact message text, wait for a clear yes, and only then call alibaba_send_message. Do not send, rewrite-and-send, or retry a send without a new approval. The extension also requires a browser confirmation for the exact conversation and message before every send. If the extension is disconnected, ask the user to open alibaba-mcp and keep the Alibaba tab open. Use alibaba_list_attachments for file names and sizes. Never ask for, display, or store Alibaba download URLs or signed links. Saving a file onto a computer needs the local companion.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| alibaba_statusA | Report the local extension connection, the access level, and whether a message.alibaba.com tab is open. Page diagnostics are included only when access is read or read/write. This does not return conversation text. |
| alibaba_list_conversationsA | List Alibaba conversations from the open messenger tab, including chats that are not on screen. Requires read or read/write access. This does not switch the open chat. |
| alibaba_get_conversationA | Read one conversation by id, including messages that are not on screen. Messages come back oldest first. This does not switch the open chat. Requires read or read/write access. Use an id from alibaba_list_conversations. |
| alibaba_send_messageA | Get the user's explicit approval before sending. Show the exact conversation and the exact message text, wait for a clear yes, and only then call alibaba_send_message. Do not send, rewrite-and-send, or retry a send without a new approval. Sends by conversation id through the messenger page and does not switch the open chat. Requires read/write access. This sends a real Alibaba message. |
| alibaba_list_attachmentsB | List file attachments in one Alibaba conversation. Requires read or read/write access. Returns ids, names, and sizes only. Remote addresses stay in the browser. |
| alibaba_download_attachmentA | Save one attachment into the private local cache and return its local path, name, size, and sha256. Requires read or read/write access. Use an id from alibaba_list_attachments. Do not ask for or display the remote address. |
| alibaba_clear_cacheA | Delete files in the private local attachment cache. This does not change anything on Alibaba. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| approve-alibaba-send | Show the exact message and require explicit user approval before alibaba_send_message. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: connection status, conversation listing, single conversation read, message send, attachment listing, attachment download, and local cache clearing. The only mild adjacency is alibaba_status versus alibaba_list_conversations, but the description explicitly says status returns no conversation text, keeping the boundary sharp.
All names share the alibaba_ prefix and follow a verb_noun convention (list_conversations, get_conversation, send_message, list_attachments, download_attachment, clear_cache). The one deviation is alibaba_status, which omits a verb, but it reads clearly enough as a diagnostic tool.
Seven tools is well within the ideal 3-15 range and each maps to a real operation in the messenger workflow. Nothing appears redundant or padding the surface.
The core lifecycle is covered: connect/status, enumerate conversations, read, send, and handle attachments plus local cache cleanup. Minor gaps remain, such as searching/filtering conversations or sending/uploading an attachment, which an agent would have to work around.