Wati vs Appwrite MCP
A side-by-side look at the Wati and Appwrite MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WatiDeveloper ToolsManage Wati contacts, conversations, campaigns, templates and Astra AI agents.35FairAuth: oauth 2.0Verdict: choose Wati for developer tools work; choose Appwrite MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
WChoose Wati when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: OAuth 2.0.
Choose Appwrite MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Wati | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 35/100 · Fair | 76/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
Tools & capabilities
Wati tools
No tool names declared yet. Check the project README from the listing page.
Appwrite MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Wati
No confirmed install command for Wati yet — follow the setup steps linked from its listing page rather than a guessed package name.
Appwrite MCP
{
"mcpServers": {
"appwrite-mcp": {
"url": "https://mcp.appwrite.io/"
}
}
}
Frequently asked questions
Wati is categorized under Developer Tools and uses an install path we have not confirmed yet. Appwrite MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Wati for developer tools work and Appwrite MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Wati has no confirmed install command yet — follow its own setup instructions.
Wati is listed as free. Auth: oauth 2.0. Appwrite MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add wati and appwrite-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wati has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Appwrite MCP has 76/100 (Great) with 3 views, 0 installs and 72 GitHub stars.