pulsemcp verified Safe content atomic mcp-remote

WeChat Official Account

This WeChat Official Account MCP server by xwang152-jack provides AI agents with direct access to WeChat's official account management capabilities through six specialized tools for authentication, content creation, media handling, and publishing. Built with TypeScript and featuring both stdio and SSE transport modes, it offers tools for OAuth authentication with WeChat's API, draft article creation and management, media upload for images and other files, permanent media asset management, and direct article publishing to WeChat official accounts. The implementation includes SQLite-based storage for credentials and media tracking, comprehensive error handling with structured logging, and a React-based web interface for configuration and testing, making it ideal for content creators, social media managers, and businesses who need AI-assisted WeChat content management and automated publishing workflows.

Cognium trust score

81%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/xwang152-jack/wechat-official-account-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve WeChat Official Account from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"