Paypal

Java-based MCP server offering JSON-RPC over HTTP and stdio interfaces to analyze authorization rates and provide a calculator tool.
  • other

0

GitHub Stars

other

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You run the PayPal MCP Server to analyze and improve payment processing by providing a JSON-RPC over HTTP API for web clients and a JSON-RPC over stdio interface for Smithery integration. It includes tools for analyzing authorization rates and a basic calculator for quick testing, helping you deploy MCP-powered capabilities in diverse environments.

How to use

You use an MCP client to connect to either the REST/HTTP API or the JSON-RPC stdio interface depending on your deployment.

How to install

Prerequisites you need before running the server are Java 17 or higher and Maven 3.6 or higher.

# Install prerequisites (example commands)
# Ensure you have Java 17+ and Maven installed on your system
java -version
mvn -version

# Build the server
mvn clean package

# Run in Web mode (REST API on port 8080)
java -jar target/paypal-java-mcp-server-0.0.1-SNAPSHOT.jar

# Run in JSON-RPC stdio mode (interactive)
java -Dspring.profiles.active=stdio -Dspring.main.web-application-type=NONE -Djsonrpc.stdio.interactive=true -jar target/paypal-java-mcp-server-0.0.1-SNAPSHOT-stdio.jar

Additional sections

Configuration and deployment notes help you tailor the MCP server to your environment. The server supports two primary modes: a web-based REST API and a JSON-RPC over stdio interface designed for Smithery deployment. For stdio mode, ensure that the process has access to stdin/stdout, and in non-interactive environments you can use a script that sets up named pipes and starts the server with interactive disabled.

If you are deploying with containerization, you can opt for Docker images that provide the REST API server and the JSON-RPC stdio server. When using the JSON-RPC stdio server in Docker, run with interactive input (the container must be started with the -i flag). A helper script can simplify running the containers in the intended mode.

Troubleshooting tips include verifying you are in the correct mode (REST vs stdio), ensuring stdin/stdout connectivity when using stdio, and checking logs for startup or runtime errors. If the server does not respond, confirm the server is running in the expected mode and that the correct connection path is used.

Available tools

improveAuthorizationRate

Analyzes transaction data to identify factors limiting authorization rates and provides actionable improvement recommendations.

calculate

Performs basic math operations to assist in testing and quick calculations during MCP usage.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational