Clawpay MCP vs Wathba
A side-by-side look at the Clawpay MCP and Wathba MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WathbaFinance & FintechSaudi payments, OTP/SMS, KYC, ZATCA e-invoicing and shipping for AI coding agents.36FairAuth: oauth 2.0Verdict: choose Clawpay MCP for finance & fintech work as a local process; choose Wathba for finance & fintech. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clawpay MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AGENT_PRIVATE_KEY, AGENT_WALLET_ADDRESS.
WChoose Wathba when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Wathba | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 56/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | AGENT_PRIVATE_KEYAGENT_WALLET_ADDRESS |
Tools & capabilities
Clawpay MCP tools
No tool names declared yet. Check the project README from the listing page.
Wathba 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.
Clawpay MCP
{
"mcpServers": {
"up2itnow0822-clawpay-mcp": {
"command": "npx",
"args": [
"-y",
"agentpay-mcp"
],
"env": {
"AGENT_PRIVATE_KEY": "YOUR_AGENT_PRIVATE_KEY_HERE",
"AGENT_WALLET_ADDRESS": "YOUR_AGENT_WALLET_ADDRESS_HERE"
}
}
}
}
Wathba
No confirmed install command for Wathba yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Clawpay MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Wathba belongs to Finance & Fintech and uses an install path we have not confirmed yet. Pick Clawpay MCP for finance & fintech work and Wathba for finance & fintech.
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. Wathba has no confirmed install command yet — follow its own setup instructions.
Clawpay MCP is listed as free. Auth: other. Wathba has no declared pricing — check the project's own site. 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 up2itnow0822-clawpay-mcp and wathba as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clawpay MCP has a quality signal of 56/100 (Good) with 4 views, 0 installs and 7 GitHub stars. Wathba has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.