Wathba

What Wathba MCP server does

The Wathba MCP server gives AI coding agents access to Wathba services through a hosted Model Context Protocol endpoint. Its covered business functions are payments, OTP and SMS delivery, KYC, ZATCA e-invoicing, and shipping. This places Saudi payment and operational workflows inside an agent interface rather than requiring the agent to implement each service connection separately.

The repository contains the official plugin package and a short skill that explains how the agent should use the available Wathba tools. The package is intended for members who authenticate through Wathba’s browser sign-in flow.

How it works

The Wathba MCP server runs remotely at https://api.wathba.info/mcp for production and https://apidev.wathba.info/mcp for development. Connections use Streamable HTTP. An MCP client discovers the server’s OAuth configuration, and the member completes authentication in a browser. The plugin itself does not handle or include API keys.

The package exposes one MCP server and carries no custom headers or scopes. Wathba determines the access grant for each connection; the consent screen describes the resulting agent access. Use either the plugin installation or a direct MCP connection, not both, to avoid duplicate tools.

Setup and configuration

Claude Code users add the Wathba marketplace, install wathba@wathba, then select the server through /mcp and sign in. Codex users can add the marketplace and install the same package, or start login with codex mcp login wathba. Installing through the ChatGPT desktop app’s Plugins page also starts sign-in.

For development, use the dev branch and the wathba-dev@wathba-development package, which points to the development endpoint. Other MCP clients can add the production or development URL as a remote Streamable HTTP server. Claude web, Claude Desktop, Claude Cowork, and ChatGPT can use the endpoint as a custom connector where supported.

Tools and capabilities

The Wathba MCP server covers these service areas:

• Payments
• OTP and SMS
• KYC
• ZATCA e-invoicing
• Shipping

The repository’s contract.json records the tools named by the shared skill and helps detect backend changes that remove or rename them.

Limitations and notes

The provided material does not specify individual tool names, request parameters, response formats, pricing, or service-specific eligibility. Access is controlled by Wathba’s server and consent flow rather than by client-side scopes. The README also distinguishes production and development environments, so credentials and data should be directed to the appropriate endpoint.

The Wathba MCP server is distributed under Apache-2.0. The repository’s CI validates generated packages, OAuth metadata, installation flows, and environment separation, but those repository workflows do not change the capabilities available to an end user.