Wagmi Tech Payment MCP Server
About
An MCP server for processing payments using stdio transport, configured via environment variables.
Details
- Author
- Wagmi-Tech-Co
- Downloads
- 246
- Categories
- Other, Cloud Service, API
Jump to
- Clean architecture with clear separation of concerns
- Docker-based deployment for easy setup
- stdio transport for direct MCP client connections
- Currently supports Moka United payment provider
- Extensible provider system for future integrations
- Configuration via environment variables or CLI options
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Wagmi Tech Payment MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Build the Docker image using docker build -t payment-mcp-server ., then configure your MCP client with the required environment variables (PROVIDER, DEALER_CODE, USERNAME, PASSWORD, CUSTOMER_TYPE_ID). Once configured, use the create_payment_link tool in your MCP client to create payment requests.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"wagmi tech payment mcp server": {
"mcp-server-payment": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROVIDER",
"-e",
"DEALER_CODE",
"-e",
"USERNAME",
"-e",
"PASSWORD",
"-e",
"CUSTOMER_TYPE_ID",
"mcp-payment-server"
],
"env": {
"PROVIDER": "moka",
"DEALER_CODE": "your_dealer_code",
"USERNAME": "your_username",
"PASSWORD": "your_password",
"CUSTOMER_TYPE_ID": "your_customer_type_id"
}
}
}
}
}McpServers
{
"mcp-server-payment": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROVIDER",
"-e",
"DEALER_CODE",
"-e",
"USERNAME",
"-e",
"PASSWORD",
"-e",
"CUSTOMER_TYPE_ID",
"mcp-payment-server"
],
"env": {
"PROVIDER": "moka",
"DEALER_CODE": "your_dealer_code",
"USERNAME": "your_username",
"PASSWORD": "your_password",
"CUSTOMER_TYPE_ID": "your_customer_type_id"
}
}
}Usage with MCP Client (e.g., Claude Desktop, Cursor)
1. Build the Docker Image
docker build -t payment-mcp-server .
2. Configure MCP Client
Add the server configuration to your MCP client (e.g., Claude Desktop, Cursor):{
"mcpServers": {
"payment-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "PROVIDER",
"-e", "DEALER_CODE",
"-e", "USERNAME",
"-e", "PASSWORD",
"-e", "CUSTOMER_TYPE_ID",
"payment-mcp-server"
],
"env": {
"PROVIDER": "moka",
"DEALER_CODE": "your_dealer_code",
"USERNAME": "your_username",
"PASSWORD": "your_password",
"CUSTOMER_TYPE_ID": "your_customer_type_id"
}
}
}
}
3. Test the Server (Optional)
# Test with environment variables
docker run -it \
-e PROVIDER="moka" \
-e DEALER_CODE="your_dealer_code" \
-e USERNAME="your_username" \
-e PASSWORD="your_password" \
-e CUSTOMER_TYPE_ID="your_type_id" \
payment-mcp-server
4. Ready to Use in MCP Client
Once configured, you can use thecreate_payment_link tool in your MCP client to create payment requests.
---
Architecture
This server follows clean architecture principles with clear separation of concerns:
- core/ - Core business logic and interfaces
- providers/ - Payment provider implementations (Moka United, extensible for others)
- utils/ - Utility functions (logging, authentication, validation)
- errors/ - Custom error handling classes
- config/ - Configuration management
Transport Mode
This server uses stdio transport for direct MCP client connections via stdin/stdout communication.
Docker Usage
Building the Image
docker build -t payment-mcp-server .
Running the Server
# Run with environment variables
docker run -it \
-e PROVIDER="moka" \
-e DEALER_CODE="your_dealer_code" \
-e USERNAME="your_username" \
-e PASSWORD="your_password" \
-e CUSTOMER_TYPE_ID="your_customer_id" \
payment-mcp-server
Or with .env file
docker run -it --env-file .env payment-mcp-server
Run with different provider (currently only moka is supported)
docker run -it \
-e PROVIDER="moka" \
-e DEALER_CODE="your_dealer_code" \
-e USERNAME="your_username" \
-e PASSWORD="your_password" \
payment-mcp-server
The server communicates via stdin/stdout for direct MCP client connection
Docker Compose Usage
# Create .env file with your credentials first
echo "PROVIDER=moka" > .env
echo "DEALER_CODE=your_dealer_code" >> .env
echo "USERNAME=your_username" >> .env
echo "PASSWORD=your_password" >> .env
echo "CUSTOMER_TYPE_ID=your_type_id" >> .env
Run the server
docker-compose up
Environment Variables
| Variable | Description | Default |
|----------|-------------|---------|
| PROVIDER | Payment provider to use | moka |
| DEALER_CODE | Payment provider dealer code | Required |
| USERNAME | Payment provider username | Required |
| PASSWORD | Payment provider password | Required |
| CUSTOMER_TYPE_ID | Customer type ID | Required |
CLI Options
| Option | Description | Default |
|--------|-------------|---------|
| --provider | Payment provider to use (env: PROVIDER) | moka |
| --dealer-code | Payment provider dealer code | Required |
| --username | Payment provider username | Required |
| --password | Payment provider password | Required |
| --customer-type-id | Customer type ID | Required |
| --host | Server host | 0.0.0.0 |
| --port | Server port | 8050 |
Logs
Logs are saved to /app/logs/ inside the container. To persist logs, mount a volume:
docker run -v ./logs:/app/logs payment-mcp-server
Support & Help
Need help setting up or using the Wagmi Tech Payment MCP Server?
Contact us: hello@wagmitech.co
We're here to help you integrate payment capabilities into your AI workflows.
This Payment MCP Server is just the beginning of our vision to make payment processing more intelligent, accessible, and integrated into the AI ecosystem.
Wagmi Tech
We're All Gonna Make It!---
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
