paystack

This MCP server exposes the full Paystack API to AI assistants via a runtime-discovered OpenAPI specification. It does not hardcode endpoints; instead, it dynamically loads operations from Paystack and presents a compact set of tools to query and execute API calls. The available tools include: get_paystack_operation to fetch details for a specific Paystack operation by its ID, get_paystack_operation_guided to infer the operation from a prompt, and make_paystack_request to execute a Paystack API request. You can also explore the list of operations with paystack://operations/list. To use it, configure your MCP client to point at the local or deployed server, provide your Paystack test secret key, and begin issuing prompts that reference Paystack actions (for example, creating a customer or listing transactions). For best results, include the keyword Paystack in your prompts to guide the LLM to the correct tools. The server validates that you supply a test key (sk_test_*) at startup for safety and sandbox usage.

Prerequisites:

• Node.js v18+
• npm or yarn
• Paystack test secret key (starts with sk_test_)

Installation steps:

1. Clone the repository: git clone https://github.com/PaystackOSS/paystack-mcp-server.git
2. Install dependencies: cd paystack-mcp-server npm install
3. Build the server: npm run build
4. Run locally (for development): PAYSTACK_TEST_SECRET_KEY=sk_test_... npm run dev
5. Start the MCP server in your environment and configure your MCP client to point to the built server as shown in the example configuration.

Tips and troubleshooting:

• Ensure you use a Paystack test secret key (sk_test_*) and that it’s provided in PAYSTACK_TEST_SECRET_KEY. Live keys are rejected.
• Node.js must be v18+ for compatibility.
• When integrating with clients, point the MCP server command to the Node binary path if needed (e.g., "command": "path/to/node" in environments where Node isn’t on the PATH).
• Use the local build path for running the server, e.g., build/index.js as shown in the example, or adjust to your deployment layout if bundling differently.
• If tools don’t appear in the client, verify the server is running and that the client’s MCP config is correctly wired to the server’s address/port.
• For debugging, you can run with npm run dev or npm run inspect to examine available operations and runtime behavior.