weflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEFLOW_BASE_URL | No | WeFlow HTTP API base URL | http://127.0.0.1:5031 |
| WEFLOW_API_TOKEN | No | Fallback token name, used if WEFLOW_ACCESS_TOKEN is empty | |
| WEFLOW_TIMEOUT_MS | No | Request timeout in milliseconds | 30000 |
| WEFLOW_ACCESS_TOKEN | No | WeFlow API token |
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
| Name | Description |
|---|---|
| weflow_healthA | Check whether the local WeFlow HTTP API is reachable. |
| weflow_list_sessionsC | List WeFlow chat sessions. Use keyword to search username or display name. |
| weflow_get_messagesC | Get messages from one WeFlow session by talker ID. Supports date ranges, keyword filtering, ChatLab format, and media export flags. |
| weflow_get_session_messages_chatlabB | Pull one session in ChatLab format using WeFlow's /api/v1/sessions/:id/messages endpoint. |
| weflow_list_contactsB | List WeFlow contacts. Use keyword to search username, nickname, remark, or display name. |
| weflow_get_group_membersB | List members of a WeChat group from WeFlow, optionally including message counts. |
| weflow_sns_timelineC | Get WeFlow Moments timeline entries. |
| weflow_sns_usernamesB | List WeFlow Moments publishers. |
| weflow_sns_export_statsC | Get WeFlow Moments export statistics. |
| weflow_sns_exportC | Export WeFlow Moments to a local directory from the WeFlow app process. |
| weflow_sns_block_deleteC | Manage WeFlow Moments anti-delete status. Actions map to status, install, and uninstall endpoints. |
| weflow_requestB | Call a custom WeFlow API endpoint. Use this for endpoints not covered by dedicated tools. |
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 12 tools
The two message retrieval tools (weflow_get_messages and weflow_get_session_messages_chatlab) have overlapping purposes; the first already supports ChatLab format, making the second redundant and confusing. Other tools are distinct within their domains.
Tool names use a consistent 'weflow_' prefix but mix verb_noun (list_sessions, get_messages), noun-only (health, request), and SNS category prefixes (sns_timeline, sns_export) inconsistently. The use of both 'list_' and 'get_' for similar actions adds inconsistency.
12 tools is appropriate for a domain covering health, chat sessions, messages, contacts, group members, and Moments. The number is well within the expected range and each tool addresses a specific sub-area.
The server provides comprehensive read and export functionality for chat and Moments, but lacks dedicated tools for sending messages or managing contacts/groups. While weflow_request can fill some gaps, core operations like sending a message are not directly exposed.