paystack

This MCP server exposes Paystack-related capabilities via the MCP protocol, allowing you to interact with your Paystack account through LLMs and automation tools. The server is built with Node.js and TypeScript and compiles to a build/index.js file that the MCP consumer invokes. It provides three main tools: get-total-transactions, create-checkout-link, and verify-transaction. Each tool accepts a JSON input payload with the required Paystack API key and relevant parameters, and returns an MCP-friendly output that summarizes results or provides the necessary data (e.g., a checkout URL). To begin, ensure your MCP consumer is configured to communicate over STDIO and point to the server’s entry point after building. The server uses standard Paystack API requests under the hood and formats responses in a consistent structure suitable for LLM-driven reasoning and downstream automation.

Prerequisites:

• Node.js (12.x or newer) and npm installed
• Git installed

Installation steps:

1. Clone the repository git clone "https://github.com/JohnnieEmmanuel/paystack-mcp-server.git"
2. Navigate to the project folder cd paystack-mcp-server
3. Install dependencies npm install
4. Build the project npm run build
5. Run the server node build/index.js
6. Connect your MCP consumer to the server via STDIO transport as documented in your MCP tooling

Notes:

• Ensure you provide Paystack API keys securely in inputs or environment as required by your workflow. The server itself does not hard-code keys.
• If you modify source, re-run the build step before starting the server.

Tips and common issues:

• Ensure your MCP consumer uses STDIO transport when connecting to the server, as described in the README.
• When testing, use test Paystack API keys (sk_test_*) to avoid live payments during development.
• Validate inputs with the provided MCP schema (e.g., apiKey, amount in Naira, email, etc.).
• If you encounter build issues, verify TypeScript compilation and Node.js compatibility with your environment.
• The get-total-transactions tool returns a summary of total count and amount; create-checkout-link returns the generated payment URL; verify-transaction returns status/details for a given reference.
• For production deployment, consider securing the API key handling and restricting access to the MCP consumer only.