Wathba MCP server
Commit Nov 15, 2026Enables AI coding agents to process Saudi payments, OTPs, and domain management through a hosted MCP server.
Also known as wathba-org/wathba-plugin, wathba-plugin
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 2.7.1
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is Wathba MCP?
Wathba enables AI coding agents to process Saudi payments, OTPs, and domain management through a hosted MCP server.
Summary generated from the project's README
About Wathba MCP server
Processing Saudi payments, managing domains, and handling OTPs through an AI coding agent is what Wathba enables. This hosted MCP server connects to clients like Claude Code, Codex, and the ChatGPT desktop app to extend their capabilities into the Wathba ecosystem. Developers can use the production server or the development environment depending on their testing needs.
Setup involves adding the specific plugin via the marketplace or connecting directly to the remote MCP server URL using Streamable HTTP transport. Security is handled through browser-based OAuth sign-in, meaning the plugin never touches or stores your API keys. Once connected, the agent gains access to tools for financial transactions and domain administration as defined by the server's permissions. The system is designed so that the client automatically discovers OAuth settings, making the connection process straightforward for users of Claude or ChatGPT.
What you can do with it
- 1Execute Saudi paymentsAsk your coding agent to process a payment through the Wathba platform.
- 2Handle OTP verificationUse the agent to facilitate one-time password processes within your application workflow.
Written from the project's README. Every use case is checked against a quote from it.
How to install Wathba MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Wathba MCP in Claude Code
$ claude mcp add --transport http wathba-plugin https://api.wathba.sa/mcpInstall Wathba MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"wathba-plugin": {
"url": "https://api.wathba.sa/mcp"
}
}
}Install Wathba MCP in VS Code
.vscode/mcp.json
{
"servers": {
"wathba-plugin": {
"type": "http",
"url": "https://api.wathba.sa/mcp"
}
}
}Install Wathba MCP in VS Code CLI
$ code --add-mcp '{"name":"wathba-plugin","type":"http","url":"https://api.wathba.sa/mcp"}'Install Wathba MCP in Codex
$ codex mcp add wathba-plugin --url https://api.wathba.sa/mcpInstall Wathba MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.wathba-plugin] url = "https://api.wathba.sa/mcp"
Install Wathba MCP in Gemini CLI
$ gemini mcp add -s user --transport http wathba-plugin https://api.wathba.sa/mcpInstall Wathba MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"wathba-plugin": {
"url": "https://api.wathba.sa/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablewathba-org/wathba-plugin is public and reachablegithub.com/wathba-org/wathba-plugin ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/wathba-org/wathba-plugin ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubWathba agent plugin
The official Wathba (وثبة) plugin for AI coding agents. It connects Codex, the ChatGPT desktop app, Claude Code and other Agent Plugins clients to Wathba's hosted MCP server, and adds one short skill that tells the agent how to use it. Payments, OTP and domains reach your app through Wathba; the plugin never handles API keys, and members sign in through the browser (OAuth).
| Environment | Branch | Install id | MCP server |
|---|---|---|---|
| Production | main |
wathba@wathba |
https://api.wathba.sa/mcp |
| Development | dev-marketplace (built from dev) |
wathba-dev@wathba-development |
https://apidev.wathba.sa/mcp |
Install
Claude Code
/plugin marketplace add wathba-org/wathba-plugin
/plugin install wathba@wathba
For the development environment, add wathba-org/wathba-plugin#dev-marketplace and
install wathba-dev@wathba-development. Then run /mcp, choose the Wathba
server and sign in. To get updates automatically, open /plugin, go to
Marketplaces, select the marketplace and choose Enable auto-update.
Codex and the ChatGPT desktop app
codex plugin marketplace add wathba-org/wathba-plugin
codex plugin add wathba@wathba
For the development environment, add --ref dev-marketplace and install
wathba-dev@wathba-development. Installing from the app's Plugins page starts
sign-in; in a terminal, run codex mcp login wathba (or wathba-dev). Codex
checks the marketplace for updates when it starts.
Any other MCP client
Add the remote MCP server URL from the table above with the Streamable HTTP transport; the client discovers Wathba's OAuth settings on its own. Claude (web, Desktop and Cowork) and ChatGPT take it as a custom connector. Use either the plugin or a direct connection, not both, or every Wathba tool appears twice.
How this repository works
Nothing under plugins/, .claude-plugin/, .agents/ or contract.json is
edited by hand. They are generated from two sources:
plugin.config.json: identities, origins, version, branding and listing text.src/: the shared skill (src/skills/wathba/SKILL.md), the icon, and the README for thedevbranch.
scripts/sync.mjs builds one marketplace per environment and enforces the
packaging rules: identities, paths, one MCP server per package with no headers
or scopes, environment isolation, no credentials, the skill's tool list, and the
icon hash.
| Workflow | When | What it does |
|---|---|---|
validate |
Every PR, push to main or dev, weekly |
Generator rules, version rule, then installs both builds into throwaway Claude Code and Codex homes, then checks the live OAuth metadata |
publish-dev |
Push to dev |
Builds the development marketplace, verifies it, and publishes it to the dev-marketplace branch |
drift |
Daily | Checks both environments' live OAuth metadata and opens an issue when it stops matching |
release |
v* tag on main |
GitHub release with the plugin ZIP, then the MCP Registry entry |
The packages carry no scopes. The Wathba server decides the grant: every connection gets full agent access, and the consent page shows exactly what that allows.
Change the plugin
Changes reach DEV first and production later, like the platform.
- Branch from
devand editplugin.config.jsonorsrc/. - Run
node scripts/sync.mjs check. - Open a pull request into
dev. When it merges,publish-devpublishes it to DEV agents as<version>-dev.<run>. No version bump is needed here. The owner's review is required: it reaches DEV members' agents.
contract.json lists the Wathba tools the skill names. The platform's CI reads
it and fails a backend change that would remove or rename one of them.
Release production
Promote once the matching Wathba platform release is in production, so the skill never names tools the production server doesn't serve yet.
- Open a pull request from
devintomainthat raisesversioninplugin.config.json. CI refuses a changed package with the same version, because Claude Code updates only when the version changes. Merge it: production installs pick it up frommain. - Tag the merge commit
v<version>and push the tag.release.ymlchecks that the tag, config and package agree, attaches the plugin ZIP,server.jsonand checksums to a GitHub release, then publishesserver.jsonto the official MCP Registry after the owner approves theregistryenvironment.
A production hotfix goes into main by its own pull request (with a higher
version); merge main back into dev right after.
listing/ holds the material for the Anthropic and OpenAI directories.
Acceptance
docs/acceptance/ records the real host journeys (sign-in, reads, project
creation, replay, recovery, update, rollback). A host is listed as supported
only after a recorded run.
License
Apache-2.0
Wathba MCP questions
How do I add Wathba MCP to Claude Code?
Run claude mcp add --transport http wathba-plugin https://api.wathba.sa/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Wathba MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I install Wathba on Claude Code?
You can install it using the commands: /plugin marketplace add wathba-org/wathba-plugin and /plugin install wathba@wathba.
Does the plugin handle my API keys?
No, the plugin never handles API keys; members sign in through the browser using OAuth.
Can I use Wathba with the ChatGPT desktop app?
Yes, you can add it using the codex plugin marketplace commands for Codex and the ChatGPT desktop app.