Connect Wathba to your coding agent

Use one MCP connection with full agent access. Your browser handles member approval; the host stores its OAuth token outside model context.

Full coding-agent access

Connect your AI coding agent

Your agent can read your projects, enabled services, pinned integration guides, operation schemas, and troubleshooting, create sandbox projects, and update an integration's API version after you confirm it in the conversation. Where Wathba offers it in the chat, it can also enable a self-serve service such as Authentica after you confirm; every other service is enabled in the portal. It never creates or reveals API keys, and it cannot fund your wallet, promote to production, or run billable operations.

OAuth · full access

Wathba MCP endpoint

https://api.wathba.sa/mcp

OAuth tokens stay in the MCP host and credentials never enter model context.

Works with Replit, Claude Code, Codex, MCP Inspector, and any Streamable HTTP MCP host that supports OAuth.

Before each integration update, the agent must explain the change, keep a working fallback, and ask for your confirmation.

Quick safety test

  1. Approve access in the Wathba browser window.
  2. Confirm the host lists the Wathba tools, including create_project and the API upgrade tools.
  3. Run list_projects, then request a Sandbox guide for Java, Go, or your repository stack.
  4. Confirm that no API-key value appears in any result.
Open setup and testing guide

Agent-managed integration updates

Every connection includes integration-update access (mcp:api-contracts:upgrade); a connection made before full access gains it when you reconnect. Wathba exposes inspect_api_upgrade, preview_api_upgrade, prepare_api_upgrade, apply_api_upgrade and rollback_api_upgrade. The agent must test both app versions, preserve a deployable fallback, prepare a scoped plan and ask you to confirm the exact update and live-app risk in your conversation. No second portal confirmation is required. Wathba records the authenticated agent’s attestation; it cannot independently verify the conversation. Never retry an uncertain payment with a different API version or key.

Wathba plugin for Claude Code and Codex

The plugin adds the Wathba MCP server and a short Wathba skill in one install. It comes from the public wathba-org/wathba-plugin marketplace.

Claude Code (type these in a Claude Code session)

/plugin marketplace add wathba-org/wathba-plugin
/plugin install wathba@wathba

Codex and the ChatGPT desktop app

codex plugin marketplace add wathba-org/wathba-plugin
codex plugin add wathba@wathba

Updates: in Claude Code, open /plugin, go to Marketplaces, select the Wathba marketplace and choose Enable auto-update. Codex checks for updates when it starts.

Use either the plugin or a direct connection from the list below, not both, or every Wathba tool appears twice.

Added a Wathba marketplace before October 2026? If the add command says the marketplace already exists, remove the old one first, then run the commands above:

/plugin marketplace remove wathba
codex plugin marketplace remove wathba

Host setup

Replit

Open Replit Integrations, add a custom remote MCP server, and enter the endpoint below. Replit opens Wathba for OAuth approval.

https://api.wathba.sa/mcp

Claude Code app

In the Claude Code app, open Settings → Connectors, choose Add custom connector, name it Wathba, paste the endpoint below, and connect.

https://api.wathba.sa/mcp
Open Claude Connectors

Claude Code CLI

Run the command once for your user account. Then run /mcp inside Claude Code, choose Wathba, and approve access in your browser.

claude mcp add --transport http --scope user wathba https://api.wathba.sa/mcp

Codex app

Add the Wathba marketplace once (see the Wathba plugin section above), then open Wathba on the Codex Plugins page, confirm the official Wathba logo and publisher, and install it. Codex opens Wathba sign-in in your browser.

Open Wathba plugin

Codex CLI

Run these commands once to add Wathba and start the browser sign-in flow. Review and approve the access yourself.

codex mcp add wathba --url https://api.wathba.sa/mcp
codex mcp login wathba

Any MCP host

For any other client, choose Streamable HTTP, paste the endpoint, and let the client discover Wathba's OAuth metadata. The client must support Authorization Code + PKCE and Dynamic Client Registration or Client ID Metadata Documents.

https://api.wathba.sa/mcp

Test with MCP Inspector

Start the official Inspector, select Streamable HTTP and the Modern (2026-07-28) protocol, enter the endpoint, connect through OAuth, then inspect Tools. Do not add an MCP-Protocol-Version custom header; the Inspector sends it.

npx @modelcontextprotocol/inspector

Acceptance checks

  1. Tools lists list_notices, list_projects, get_project_setup, list_project_services, get_service_integration_docs, get_service_operations, get_service_troubleshooting, recommend_services_for_repository, create_project, and the API upgrade tools inspect_api_upgrade, preview_api_upgrade, prepare_api_upgrade, apply_api_upgrade and rollback_api_upgrade. create_project makes sandbox projects only.
  2. Wathba speaks MCP protocol 2026-07-28 (hosts that only support earlier revisions still connect) and exposes no resources. Every tool result, including errors, is one JSON object in structuredContent.
  3. list_project_services separates configuredServices from availableServices. Where Wathba offers it in the chat, a self-serve service's nextAction opens a card in which you enable it; you enable every other service yourself on the portal page it links to.
  4. A project owned by another member is denied.
  5. Java, Go, PHP, .NET, Python, cURL, JavaScript, TypeScript, and other stacks return direct HTTP guidance.
  6. No result contains an API key, provider credential, secret handle, or mutation instruction.
  7. No tool creates or reveals an API key, funds the wallet, promotes to production, or sends OTP/payment/shipping calls. Production environments and services are set up in the portal, apart from a self-serve service where Wathba offers it in the chat.

Useful first prompt

Use Wathba to list my projects. Ask me which project and service I mean, inspect my repository locally to identify its language and HTTP stack, then read the pinned Sandbox integration guide. Do not request, display, or manage any API key.