| FMRS | 47 / 100 · D | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 5 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 6 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 18 / 20 | 14 / 20 |
|---|
| Best for | - Developers and hobbyists wanting a self-hosted WhatsApp API gateway
- Scenarios requiring WhatsApp automation integrated into AI agents
- Personal projects or internal tools needing low-cost messaging automation
- Developers willing to accept unofficial API risks and account restrictions
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Production environments requiring official WhatsApp Cloud API compliance (e.g., healthcare, finance, large-scale commercial messaging)
- Users who cannot accept account ban risks
- Users wanting zero-configuration setup (requires some deployment and configuration)
- Scenarios needing full REST API coverage (MCP exposes only curated tools)
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Requires API key authentication (role OPERATOR or lower, session-scoped)
- May require access to the Docker socket (if using built-in orchestration, protected by docker-proxy)
- MCP endpoint must be reachable from the client (e.g., localhost or LAN)
- Recommended to use a dedicated WhatsApp number to avoid risks to primary numbers
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - Unofficial WhatsApp API, risk of account restriction or ban
- Messages may be dropped by WhatsApp server-side (first message to new contacts)
- Requires regular updates to dependencies to cope with WhatsApp protocol changes
- If /mcp is exposed publicly without an auth proxy, it could be abused
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, Cursor | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 1 | 2 | 15 |
|---|