Best for
- Developers building WeChat applications with .NET / C#
- Technical evaluators tracking new MCP integration in the Senparc.Weixin SDK
W
WeChat MCP Server
Community
WeChat MCP Server based on WeiXinMPSDK (WeChat McpRouter)
- Category
- Other #205 of 230
- Stars
- ★ 8.9k Very popular
- Transport
- stdio (local process)
- Runtime
- .NET
- Credentials
- API key / credential required
- License
- Apache-2.0
- Last commit
35FMRS · D
This MCP server is part of the Senparc.Weixin WeChat .NET SDK repository; its manifest describes it as a "WeChat MCP Server using WeChat McpRouter" at version 0.1.0-beta. Beyond the repository's own WeChat full-platform SDK capabilities, the source provides no tool list, transport, authentication or installation details, and the NuGet package name remains a placeholder, so it is currently suitable only for tracking and experimentation, not production use.
Strongest · Maintenance 15/20 Weakest · Reliability 4/20
Why each score
- Reliability 4/20
- Static review exposes only the manifest at src/Senparc.Weixin.MCP.Server/.mcp/server.json; no MCP server source, tool definitions, CI workflows, or test files are provided. The manifest's packages[0].name is still the placeholder "<your package ID here>", contradicting the name/version declared in the same file, so an installer cannot resolve a real package and even a clean MCP init plus tools/list handshake cannot be verified from source. The repository is a mature WeChat .NET SDK, but that does not substitute for execution evidence for this MCP server. With no verifiable happy path and a visible contradiction, the score is low.
- Security and permissions 6/20
- No malware, credential theft, or covert exfiltration was found, and no real tokens or secrets appear in the README or manifest, so no red line is triggered. However, evidence is very thin: the manifest declares empty environment_variables and package_arguments and never states how the MCP server obtains sensitive WeChat credentials (AppId, AppSecret, Token, EncodingAESKey). The README stresses appsettings.json configuration and automatic AccessToken custody, but there is no MCP-level least-privilege scoping, confirmation flow for side-effecting WeChat APIs (customer-service messages, mass send, payment endpoints), or data-boundary disclosure. Credential handling and side-effect confirmation are invisible, so the score stays low.
- Maintenance 15/20
- The Apache-2.0 license is explicit and consistent between README and license file. The project claims over 13 years of maintenance and shows master/Developer branch policy, NuGet publishing artifacts, a contributor list, NuGet download badges, and a build-status badge, indicating established governance and release channels. But the MCP submodule is 0.1.0-beta with a placeholder package name, showing it is not release-ready, and there is no security-response channel (e.g., SECURITY.md) or MCP-specific versioning documentation. Sustained maintenance exists while submodule governance and versioning remain incomplete, hence a mid-to-high score.
- Documentation 6/20
- The README is an extensive SDK guide, yet it contains no MCP-server-specific section on installation, authentication, tool inventory, parameters, limits, cost, or troubleshooting, so the exposed tools and their behavior cannot be determined. The manifest description is a single line, "WeChat MCP Server using WeChat McpRouter", with no tool-level documentation, and the placeholder package name further divorces docs from implementation. SDK examples are plentiful but barely help this review target. The reviewable evidence gap is material, so the score is low.
- Setup experience 4/20
- The manifest supplies only a repository path: no install command, no client configuration example, no runtime prerequisites such as the required .NET version or how to obtain WeChat credentials, and the package name is a placeholder, so a mainstream client cannot complete setup from the given material. Fork and Sample steps belong to SDK development, not MCP connection. Platform compatibility and dependency notes are absent. Under the static calibration rule the cap is 15 without execution evidence, and here even the basic install path is incomplete, so the score is very low.
Static review · not runListed 2026-09-18
Read the FMRS scoring method →Fit and risk
What it can accessUses the network
Not for
- Users needing a stable, production-released MCP server (currently 0.1.0-beta with an unfilled package name)
- Users outside the .NET stack or without a need for WeChat platform capabilities
- Users requiring a definite tool list and complete installation documentation
Required permissions
- The source does not state the permissions or scopes required by this MCP server.
Risks and side effects
- The NuGet package name in the manifest is a placeholder, so the actual installable package cannot be confirmed and installation may fail.
- The version is 0.1.0-beta, so interfaces and behavior may change at any time.
- The source provides no tool, authentication or permission details, leaving the security boundary unknown.
Setup
Before you start
Runtime：.NET
No installation instructions are provided in the source. The manifest lists NuGet as the registry with the placeholder package name "<your package ID here>" at version 0.1.0-beta, so an actionable install procedure cannot be given.
Check that it works
This MCP server (io.github.JeffreySu/WeixinMPSDK, 0.1.0-beta) is in beta and the manifest's NuGet package name is still the placeholder '<your package ID here>', so no documented install command exists. After configuration, confirm the server appears in your client's tool list with its exposed tools; calls require configured WeChat Official Account / Mini Program credentials.
Troubleshooting
- Verify whether the package name has been replaced with a real NuGet package ID in the manifest; otherwise installation will fail.
- Check that the version matches the repository branch (manifest states 0.1.0-beta).
- Check src/Senparc.Weixin.MCP.Server/.mcp/server.json in the repository for an updated version.
- Confirm the development environment supports .NET (the repository states support for .NET Framework, .NET Core and .NET 10.0).
Things to try
Once connected, you can ask your AI assistant things like:
- Send a text customer-service message to a given OpenId via the WeChat Official Account API
- List the tools exposed by this WeChat MCP server and explain what they do
Use cases
Experimenting with MCP integration for WeChat capabilities in a .NET project
Exploring the MCP (McpRouter) integration direction of the Senparc.Weixin SDK
Overview
This is an MCP server bundled in the Senparc.Weixin (WeChat full-platform .NET SDK) repository, located at src/Senparc.Weixin.MCP.Server/.mcp/server.json, with the manifest describing it as a "WeChat MCP Server using WeChat McpRouter". The repository itself is an open-source .NET SDK covering WeChat Official Accounts, Mini Programs, Mini Games, WeChat Pay, WeCom/Enterprise Accounts, Open Platform, JSSDK and more, and has been maintained for over 13 years. The manifest still lists a placeholder NuGet package name (<your package ID here>) at version 0.1.0-beta, indicating an early beta state. Because the source provides no tool list, transport details or installation example, the available tools and invocation method cannot be confirmed.
Similar servers
Hevy MCP
77 · B
Manage your Hevy workout data from AI assistants via MCP.
Firecrawl MCP Server
75 · B
Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
BioMCP
75 · B
One binary. One grammar. Evidence from the biomedical sources you already trust.
Compartment
75 · B
Encrypted, fully offline long-term memory for AI agents
Source revision 327a77fd15b4 Data synced 2026-11-02 Read the FMRS scoring method