wechat-mp-publisher_skill

Overview

This skill enables compliant remote publishing to WeChat Official Accounts by routing publish requests through a remote MCP (wenyan-mcp) server. It solves home broadband IP volatility by centralizing a stable MCP endpoint while keeping credentials isolated from system configuration. The skill includes dependency checks, flexible MCP configuration, and command-line scripts for advanced users.

How this skill works

The skill reads WeChat credentials from a local wechat.env file and validates required tools (jq, mcporter, wenyan-cli) before publishing. Publish requests are proxied to a configured remote MCP server (SSE/HTTP), so only the remote server IP needs to be added to the official account whitelist. Scripts and the assistant interface call the remote MCP to upload articles and assets, while keeping credentials and configuration separated for compliance.

When to use it

• You need to publish WeChat articles from a network with a non-static or frequently changing IP.
• You want to avoid adding multiple local IPs to the WeChat IP whitelist.
• You must separate publishing credentials from global system tooling for audit or compliance.
• You prefer a simple assistant-driven publish flow but want CLI parity for automation.
• You need automatic dependency checks before attempting a publish.

Best practices

• Keep wechat.env outside version control and load it only at runtime to protect credentials.
• Add only the remote MCP server public IP to the WeChat IP whitelist, not local device IPs.
• Use an image host (CDN or imgur-like service) for cover images so the remote server can fetch them reliably.
• Verify mcp.json points to your remote wenyan-mcp instance and include an API key header if available.
• Install and validate jq, mcporter, and wenyan-cli on the publishing host to avoid runtime failures.

Example use cases

• Publish a blog post from a laptop on public Wi‑Fi without exposing your home IP to the whitelist.
• Automate scheduled WeChat article pushes from a CI runner that lacks a fixed IP.
• Give multiple contributors local publishing ability while centralizing whitelist management to a single MCP IP.
• Integrate with content workflows: use the assistant to publish drafts or use scripts in deployment pipelines.
• Troubleshoot publishing failures with pre-flight dependency and config checks before calling the remote MCP.