Wathba

io.github.wathba-orgv2.0.1更新于 Oct 1, 2026

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

已验证Streamable HTTP可网页运行Developer ToolsBusiness & Commerce

概览

AI 生成的概览

将 AI 编程代理连接到 Wathba 托管的 MCP 服务器，用于沙特支付、OTP/短信、KYC、ZATCA 电子发票和物流。

功能
Wathba 是官方插件，把 AI 编程代理连接到 Wathba 托管的 MCP 服务器（R2、R3）。通过它，助手可以使用 Wathba 的支付、OTP/短信、KYC、ZATCA 电子发票和物流服务（R4）。插件还会添加一段简短技能说明，告诉代理如何使用该服务器（R3），服务器暴露的工具列表记录在 contract.json 中（R40）。
适用场景
当你正在构建或运营需要沙特市场服务的应用（如支付、OTP/短信验证、KYC、ZATCA 电子发票或物流），并希望 AI 编程代理直接调用这些服务时使用（D1、R4）。它适合已使用 Wathba 作为服务商的团队，而非通用代理任务。如果不需要这些服务或没有 Wathba 账户，则不必安装。
运行要求
需要访问远程 Streamable HTTP MCP 服务器：生产环境为 API 密钥或环境变量；成员通过浏览器 OAuth 登录（R4、R10、R14）。支持 Claude Code、Codex、ChatGPT 桌面应用、Claude 网页版/桌面版/Cowork 及其他 MCP 客户端（R3、R18）。需要能访问 Wathba 端点的网络。
安装前请注意
每个连接都会获得对 Wathba 账户的完整代理访问权限，授权页面会显示具体允许的内容（R32），批准前请仔细查看。插件本身不处理 API 密钥，登录通过浏览器 OAuth 完成（R4），但相关工具可能发起支付、发送 OTP/短信、提交 KYC 资料、开具 ZATCA 电子发票和安排物流，因此操作可能涉及资金变动或向第三方发送数据。请只使用插件或直连中的一种，否则每个工具都会出现两次（R19）。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Wathba，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "wathba": {
      "type": "http",
      "url": "https://api.wathba.info/mcp"
    }
  }
}

README

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.info/mcp
Developmentdevwathba-dev@wathba-developmenthttps://apidev.wathba.info/mcp

Install

Claude Code

text
/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

sh
codex plugin marketplace add wathba-org/wathba-plugincodex 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

来源：README.md，提交 a14db87

工具

0
工具元数据尚未被收录。

版本历史

1
  1. v2.0.1最新Oct 1, 2026