@imazhar101/paypal-mcp
Related Servers
Alternatives to @imazhar101/paypal-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityNot gradedmaintenanceThis is an MCP server to manage PayPal12-
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to PayPal data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcpMIT
- AlicenseNot gradedqualityBmaintenanceEnables natural-language PayPal operations such as creating and sending invoices, reminders, payment search, refunds, and account summaries through a self-hosted Streamable HTTP interface backed by the PayPal REST API. It includes a mock transport for credential-free testing.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides comprehensive integration with PayPal's APIs, enabling seamless interaction with payment processing, invoicing, subscription management, and business operations through a standardized interface.7Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for PayMongo payment gateway (Philippines). Supports payment intents, sources, payments, refunds, and checkout sessions via Basic Auth.2411 npm2MIT
- AlicenseBqualityFmaintenanceA comprehensive Model Context Protocol (MCP) server for BTCPayServer integration, providing tools for payment processing, store management, user administration, webhook handling and more with full API coverage.316 npm3MIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action (e.g., get_ vs list_), and all resource types are clearly separated (balances, captures, disputes, invoices, orders, subscriptions, plans, transactions). No two tools have overlapping purposes.
All tools follow a consistent 'paypal_verb_noun' pattern in snake_case, with clear verbs like get, list, and verify. No mixing of conventions or vague verbs.
With 11 tools, the server covers a reasonable breadth of PayPal operations without being excessive. Each tool addresses a clear use case, and the count feels appropriate for a focused integration.
The server is entirely read-only except for credentials verification. Missing create, update, or delete operations for any resource (e.g., orders, invoices, disputes) severely limits its utility for typical payment workflows.