Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Saudi payments, OTP and domains for AI coding agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.wathba.sa/mcpRun this in your terminal
claude mcp add --transport http wathba https://api.wathba.sa/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wathba": {
"url": "https://api.wathba.sa/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"wathba": {
"type": "http",
"url": "https://api.wathba.sa/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.wathba.sa/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account wathba-org, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 937 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (2.7.1) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 |
/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 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.
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.
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.
| 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.
Changes reach DEV first and production later, like the platform.
dev and edit plugin.config.json or src/.node scripts/sync.mjs check.dev. When it merges, publish-dev publishes it to DEV agents as -dev. . 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.
Promote once the matching Wathba platform release is in production, so the skill never names tools the production server doesn't serve yet.
dev into main that raises version in plugin.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 from main.v 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.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.
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.
Apache-2.0