Wathba

Registre officiel Outils de développement

Saudi payments, OTP/SMS, KYC, ZATCA e-invoicing and shipping for AI coding agents.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http wathba 'https://api.wathba.sa/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "wathba": {
            "type": "http",
            "url": "https://api.wathba.sa/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Wathba agent plugin
  2. Install
  3. How this repository works
  4. Change the plugin
  5. Release production
  6. Acceptance
  7. License

Wathba 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/SMS, KYC, ZATCA e-invoicing and shipping reach your app through Wathba; the plugin never handles API keys, and members sign in through the browser (OAuth).

EnvironmentBranchInstall idMCP server
Productionmainwathba@wathbahttps://api.wathba.sa/mcp
Developmentdevwathba-dev@wathba-developmenthttps://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 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 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 the dev branch.

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.

WorkflowWhenWhat it does
validateEvery PR, push to main, weeklyGenerator rules, version rule, then installs both builds into throwaway Claude Code and Codex homes, then checks the live OAuth metadata
publish-devPush to mainBuilds the development marketplace, verifies it, and publishes it to the dev branch
driftDailyChecks both environments' live OAuth metadata and opens an issue when it stops matching
releasev* tag on mainGitHub 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

  1. Edit plugin.config.json or src/.
  2. Run node scripts/sync.mjs check.
  3. If the production package changes, raise version in plugin.config.json. CI refuses a changed package with the same version, because Claude Code updates only when the version changes.
  4. Open a pull request. Every change here reaches members' agents, so the owner's review is required.

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

  1. Merge the change (with its higher version) to main. Plugin installs pick it up from main.
  2. Tag the merge commit v<version> and push the tag. release.yml checks that the tag, config and package agree, attaches the plugin ZIP, server.json and checksums to a GitHub release, then publishes server.json to the official MCP Registry after the owner approves the registry environment.

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

Questions fréquentes

Qu'est-ce que Wathba ?

Saudi payments, OTP/SMS, KYC, ZATCA e-invoicing and shipping for AI coding agents.

Comment installer Wathba ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http wathba 'https://api.wathba.sa/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Wathba ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Wathba est-il open source ?

Oui. Son code est sur GitHub sous licence Apache-2.0.

Qui maintient Wathba ?

Il est publié par wathba-org. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.