Omnisockit Mcp
Wire your coding agent to WeCom (企业微信) with curated skills and hundreds of documented APIs instead of guessing endpoints from scattered docs.
Overview
OmniSocKit omnisockit-mcp is a MCP server for the Build phase that gives coding agents WeCom-focused skills and access to 550+ enterprise messaging APIs.
What is this MCP server?
- Advertises 41 bundled SKILL-style capabilities aimed at WeCom development workflows
- Exposes 550+ WeCom-related APIs through one MCP server
- stdio npm package @omnisockit/mcp-server for local agent hosts
- Positions the agent as a WeCom development specialist rather than a generic chat assistant
- Version 0.1.5 on the official MCP server schema
- 41 SKILLs advertised for WeCom development
- 550+ APIs exposed through the server
- Package version 0.1.5 (@omnisockit/mcp-server)
What problem does it solve?
WeCom API surface is broad and easy to misuse without structured guidance, which slows indie builders shipping bots and internal apps.
Who is it for?
Indie builders or micro-teams shipping WeCom bots, approvals, or CRM hooks who already use Claude Code, Cursor, or Codex with MCP.
Skip if: Builders with no WeCom tenant, or products that only target global Slack, Discord, or email workflows.
What do I get? / Deliverables
After you install the npm MCP server, your agent can call WeCom operations and follow packaged skills instead of improvising from incomplete documentation.
- Agent-callable WeCom API operations via MCP tools
- Access to 41 advertised skill-oriented development workflows
- Faster iteration on WeCom bot and integration code in-repo
Recommended MCP Servers
Journey fit
Enterprise messaging integrations are implemented during product build when you connect internal tools, bots, and workflows to WeCom. Integrations subphase is where third-party platform APIs and agent-accessible tooling are added to the stack.
How it compares
WeCom-focused MCP API bridge, not a generic markdown agent skill or a hosted no-code bot builder.
Common Questions / FAQ
Who is io.github.OmniSocKit/omnisockit-mcp for?
It is for developers and solo founders integrating WeCom into SaaS, internal tools, or agent-driven workflows who want MCP-native API coverage plus bundled development skills.
When should I use io.github.OmniSocKit/omnisockit-mcp?
Use it during Build when you are implementing WeCom messaging, contacts, or app callbacks and need the agent to propose correct API calls against a large catalog.
How do I add io.github.OmniSocKit/omnisockit-mcp to my agent?
Add the @omnisockit/mcp-server npm package to your MCP client configuration with stdio transport, following your host’s MCP settings (Claude Code, Cursor, etc.), and supply WeCom credentials your app already uses.