Oman Payments Mcp

What is Oman Payments MCP?

Oman Payments MCP is a remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor, etc.) accept payments in Oman using Tap Payments’ hosted checkout. It supports cards, Apple Pay, and other methods enabled on the merchant’s Tap account. The server is a stateless translation layer — funds flow directly from buyer to Tap Payments to the merchant, and no credentials or data are stored.

How to use Oman Payments MCP?

Connect any MCP client to the endpoint https://mcp-om.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC). Set the HTTP header x-tap-secret-key to your Tap Payments secret key (test keys start with sk_test_, live keys with sk_live_). Use the provided tools: create_payment_link to generate an OMR hosted-checkout link, and query_payment_status to check if a payment is paid.

Key features of Oman Payments MCP

• Stateless translation layer with no database.
• Never holds funds or stores credentials.
• Supports OMR (Omani Rial) payments via Tap Payments.
• Provides a hosted checkout link for card/Apple Pay.
• Pull-based payment status check (paid=true when complete).
• Remote MCP server with Streamable HTTP transport.

Use cases of Oman Payments MCP

• AI agents accepting e-commerce payments in Oman.
• Automating invoice generation and payment collection.
• Enabling chatbots or assistants to handle checkout flows.
• Building payment-enabled applications without managing PCI compliance.

FAQ from Oman Payments MCP

How does this server differ from a direct payment gateway integration?

It is a stateless MCP translation layer that delegates all payment processing to Tap Payments. Funds move directly buyer → Tap Payments → merchant; the server never touches or stores financial data.

What runtime or dependencies are required to use the server?

Clients only need an MCP-compatible client (e.g., Claude, ChatGPT). For local development, Node.js ≥ 18 is required; the server itself has zero runtime dependencies.

Where does payment data live?

The server has no database and stores no data. All payment information is handled by Tap Payments; the server only relays requests and responses.

What transport protocol does the server use?

It uses Streamable HTTP with stateless JSON-RPC messages.

How is authentication handled?

Authentication is done via the x-tap-secret-key HTTP header, which must contain your Tap Payments secret key (test or live).