Skip to main content
Glama
SsssssSynqa

WeChat MCP Server

by SsssssSynqa

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WECHAT_MCP_KEYSNoPath to the wechat_keys.json file. Default search order: environment variable, current directory, ~/.wechat-mcp/wechat_keys.json
WECHAT_MCP_DB_BASENoBase directory for the WeChat database files. Default is auto-detected based on OS (macOS: ~/Library/Containers/com.tencent.xinWeChat/Data/Documents/xwechat_files, Windows: %USERPROFILE%\Documents\xwechat_files)

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_recent_sessionsA

获取微信最近会话列表,包含最新消息摘要、未读数、时间等。 用于了解最近有哪些人/群在聊天。

get_chat_historyB

获取指定聊天的消息记录。支持模糊匹配联系人名/备注名,支持按日期范围筛选。

search_messagesA

在所有聊天记录中搜索包含关键词的消息。

get_contactsA

搜索或列出微信联系人。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct data access pattern: recent sessions, chat history for a specific chat, keyword search across all chats, and contact lookup. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern (get_recent_sessions, get_chat_history, search_messages, get_contacts). The use of 'search' instead of 'get' is semantically appropriate and maintains consistency in structure.

Tool Count5/5

Four tools is well-scoped for a read-only WeChat query server. Each tool covers a distinct aspect of the domain (sessions, history, search, contacts) without redundancy or bloat.

Completeness4/5

The tools cover all major read operations for WeChat data. Missing operations like sending messages or managing contacts may be intentional given the read-only nature implied by the tool set, but a send_message tool would be a common expectation for a full-featured WeChat server.

Maintenance

ActivityInactive
ResponsivenessUnresponsive