Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"paystack": {
"args": [
"@paystack/mcp-server",
"--api-key",
"sk_test_..."
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that enables AI assistants to interact with the full range of Paystack APIs.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@paystack/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @paystack/mcp-server against OSV.dev.
Click any tool to inspect its schema.
paystack_operation_listList all available Paystack operations and their details
paystack://operations/list
paystack_skillKnowledge resource with documentation, code snippets, and API details
paystack://skill
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol server for building an investor agent
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
Remote MCP server to integrate and validate self-hosted PayRam deployments.
MCP Security Weekly
Get CVE alerts and security updates for Paystack Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that enables AI assistants to interact with the full range of Paystack APIs.
[!WARNING] Public Preview: This MCP server is currently in public preview. We're seeking early feedback to improve the next iteration, so use cautiously and report any issues you encounter.
Install and run via npm (recommended):
npx @paystack/mcp-server --api-key sk_test_your_key_here
Or for local development, clone and build:
git clone https://github.com/PaystackOSS/paystack-mcp-server.git
cd paystack-mcp-server
npm install
npm run build
Then configure your MCP client to use the server (see Client Integration).
sk_test_)| Environment Variable | Purpose |
|---|---|
PAYSTACK_TEST_SECRET_KEY | Your Paystack test secret key (fallback if no CLI arg) |
You can provide your API key in two ways:
--api-key sk_test_...PAYSTACK_TEST_SECRET_KEYSecurity note: Only test keys (
sk_test_*) are allowed. The server validates this at startup and will reject live keys.
The Paystack MCP Server works with any MCP-compatible client. Below is the standard configuration schema used by most clients (Claude Desktop, ChatGPT Desktop, Cursor, Windsurf, etc.).
For npm-installed server:
{
"mcpServers": {
"paystack": {
"command": "npx",
"args": ["@paystack/mcp-server", "--api-key", "sk_test_..."]
}
}
}
If you've cloned and built the server locally:
{
"mcpServers": {
"paystack": {
"command": "node",
"args": ["/path/to/paystack-mcp-server/build/index.js"],
"env": {
"PAYSTACK_TEST_SECRET_KEY": "sk_test_..."
}
}
}
}
[!IMPORTANT] When setting
command: "node", you should ensure you're using Node v18+. If you are using a package manager, you might need to get the path of your Node binary by running this command in your CLI:Linux and MacOS
which nodeWindows
where nodeOnce you have the path, use it as the value of the MCP Server command in the JSON configuration. e.g.,
command: "path/to/installation/bin/node"
| Client | Config file location |
|---|---|
| VS Code | .vscode/mcp.json |
| Claude Desktop | claude_desktop_config.json |
| ChatGPT Desktop | MCP settings in app preferences |
| Cursor | .cursor/mcp.json or global MCP settings |
| Windsurf | MCP configuration in settings |
| Claude Code | ~/.claude/mcp.json or project-level .mcp.json |
The Paystack MCP Server exposes the entire Paystack API to AI assistants by parsing Paystack's OpenAPI specification at runtime. Instead of hardcoding individual endpoints, the server dynamically discovers all available operations and makes them accessible through a small set of tools.
| Tool | Description |
|---|---|
get_paystack_operation | Fetch operation details (method, path, parameters) by operation ID |
make_paystack_request | Execute a Paystack API request |