weflow-mcp
Enables to access and manage WeChat data (sessions, contacts, Moments) through the local WeFlow HTTP API.
README
weflow-mcp
TypeScript MCP server for calling the local WeFlow HTTP API.
WeFlow must be running locally with API 服务 enabled. The default API base URL is http://127.0.0.1:5031. Except for health checks, WeFlow /api/v1/* endpoints require an access token.
Install
Use directly with npx:
npx -y weflow-mcp
Or install from source:
npm install
npm run build
Configuration
Set these environment variables in your MCP client:
| Variable | Default | Description |
|---|---|---|
WEFLOW_BASE_URL |
http://127.0.0.1:5031 |
WeFlow HTTP API base URL |
WEFLOW_ACCESS_TOKEN |
empty | WeFlow API token |
WEFLOW_API_TOKEN |
empty | Fallback token name, used if WEFLOW_ACCESS_TOKEN is empty |
WEFLOW_TIMEOUT_MS |
30000 |
Request timeout in milliseconds |
MCP client example
{
"mcpServers": {
"weflow": {
"command": "node",
"args": ["/home/projects/wechat-tool/weflow-mcp/dist/index.js"],
"env": {
"WEFLOW_BASE_URL": "http://127.0.0.1:5031",
"WEFLOW_ACCESS_TOKEN": "YOUR_TOKEN"
}
}
}
}
After npm publish, you can use npx instead:
{
"mcpServers": {
"weflow": {
"command": "npx",
"args": ["-y", "weflow-mcp"],
"env": {
"WEFLOW_BASE_URL": "http://127.0.0.1:5031",
"WEFLOW_ACCESS_TOKEN": "YOUR_TOKEN"
}
}
}
}
Tools
weflow_health: check WeFlow API health.weflow_list_sessions: list chat sessions.weflow_get_messages: get messages from a chat session.weflow_get_session_messages_chatlab: pull one session in ChatLab format.weflow_list_contacts: list contacts.weflow_get_group_members: list group members.weflow_sns_timeline: get Moments timeline.weflow_sns_usernames: list Moments publishers.weflow_sns_export_stats: get Moments export stats.weflow_sns_export: start a Moments export.weflow_sns_block_delete: get/install/uninstall Moments anti-delete status.weflow_request: call any supported WeFlow API endpoint with custom method/query/body.
Notes
- WeFlow's API only listens on
127.0.0.1by default. - Before using data tools, connect WeFlow to the WeChat database in the WeFlow app.
- Media URLs returned by message APIs are usable after calling messages with
media=1.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.