razorpay-mcp
Related Servers
Alternatives to razorpay-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA remote MCP server that lets any AI agent accept payments in India via UPI, cards, netbanking, and wallets through Razorpay Payment Links. Bring your own credentials, stateless, no funds touched.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for ClawVault - an AI agent payment security layer that enables Claude to request payments, check limits, and manage transactions with configurable rules.74 npmMIT
- FlicenseNot gradedqualityCmaintenancePayDesk MCP is a production-grade Model Context Protocol (MCP) server that exposes payment gateway APIs, tools, prompts, and resources. It bridges the gap between an AI assistant and three underlying database systems to resemble real payment services like Stripe, Razorpay, or PayPal.-
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI assistants like Claude to your Chatwoot instance. Manage customer conversations, read messages, send replies, and filter by date ranges -- all through natural language.549 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that integrates Safaricom's M-PESA Daraja API with Claude, enabling natural language payment processing and real-time transaction notifications.3-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for integrating Xero with GenAI applications.-
TDQS
Scored across 14 tools
Every tool targets a distinct resource or analysis type (customers, orders, payments, refunds, subscriptions, dashboard, failed payment analysis), with no overlapping purposes. An agent can clearly differentiate between them.
All tools follow a consistent verb_noun pattern using lowercase and underscores: 'get_' for single items and 'list_' for collections. No mixing of conventions.
14 tools is well-scoped for a payment gateway MCP, covering all major entities and analytics without being excessive or insufficient.
The tool surface is entirely read-only (get and list operations), lacking any create, update, or delete tools. For a payment gateway, this is a significant gap that prevents agents from taking actions like creating payments or refunds.