Paypal Java MCP Server

🚀 PayPal Java Project Documentation

This is a Java project for managing PayPal account transaction data. It provides two main functional modules: analyzing transaction authorization rates and basic mathematical operation tools.

🚀 Quick Start

This Java project is designed to manage PayPal account transaction data. It comes with two key functional modules: one for analyzing transaction authorization rates and another for basic mathematical operations.

✨ Features

Authorization Rate Analysis Tool

This tool analyzes transaction data and offers suggestions to improve the authorization rate.

Parameter Description:

• merchantId (Required): The merchant ID to be analyzed.
• timeFrame (Optional): The time frame for analysis, defaulting to "last_30_days".
• transactionType (Optional): Transaction type filter, defaulting to "all".

Calculator Tool

This tool is used to perform basic mathematical operations.

Parameter Description:

• operation (Required): The operation to be performed, including add, subtract, multiply, and divide.
• a (Required): The first operand.
• b (Required): The second operand.

Docker Deployment

The project includes Docker support for both the REST API server and the JSON - RPC standard input - output server.

Building Docker Images

Building Two Images Using Docker Compose

docker-compose build

Building the REST API Server Image Separately

docker build --target rest-api -t paypal-mcp-rest-api .

Building the JSON - RPC Server Image Separately

docker build -f Dockerfile.smithery -t paypal-mcp-jsonrpc .

Starting Docker Containers

Starting the REST API Server

docker run -p 8080:8080 paypal-mcp-rest-api

Starting the JSON - RPC Server

Since the JSON - RPC server interacts via standard input and output, it must be run in interactive mode:

docker run -i paypal-mcp-jsonrpc

Or use the provided script:

./run-docker.sh

Starting with Docker Compose

Starting the REST API server:

docker-compose up rest-api

Note: The JSON - RPC standard input - output server is usually not run directly through Docker Compose because it requires standard input - output interaction.

📚 Documentation

Troubleshooting

"The server's tool list cannot be accessed via the network"

If you see an error indicating that the server's tool list cannot be accessed via the network, it may be because:

1. You are trying to access the server via the HTTP protocol while the server is running in standard input - output mode.
2. The server was not started in interactive mode.
3. The -Djsonrpc.stdio.interactive=true flag is missing from the startup command.

Solution:

• Ensure that the JSON - RPC standard input - output interface is used.
• When using Docker, run the server in interactive mode (add the -i flag).
• Add the -Djsonrpc.stdio.interactive=true flag to the startup command.
• If in a non - interactive environment, use the start - non - interactive.sh script.

"The server cannot be initialized in a non - interactive environment"

If the server fails to start properly in a non - interactive environment:

1. Use the specially designed start - non - interactive.sh script.
2. Add the -Djsonrpc.stdio.interactive=false flag to the startup command.
3. Ensure that the Docker container is configured with the correct resource permissions.

Solution:

./start-non-interactive.sh

"Unable to connect to the database"

If you encounter an error indicating that you cannot connect to the database, check the following:

1. Whether the database service is started and running.
2. Whether the database connection parameters (such as address, port, username, and password) are correctly configured.
3. Whether there are any network connection issues.

Solution:

# Restart the database service
sudo systemctl restart postgresql

# Check the database listening address settings
vi /etc/postgresql/main.conf

📄 License

The project uses the Apache License, Version 2.0. For specific license details, please refer to the LICENSE file.

# View the license agreement content
cat LICENSE