
Paystack Mcp
io.github.tracentdevPublished by GitHub account tracentdevv0.1.1Updated Oct 24, 2026
Agent-callable Paystack for African commerce. Ten tools, integer-kobo money, NDPA-compliant.
Overview
A local MCP server that gives an assistant agent-callable access to Paystack, the African payments platform, through ten tools using integer-kobo amounts.
- What you can do
- Call Paystack payment operations through ten tools, with amounts handled as integer kobo rather than decimals. The description frames it as agent-callable Paystack for African commerce and mentions NDPA-compliant handling. The manifest lists no individual tools, so the exact set of operations is not documented here.
- When to use it
- Worth considering when an assistant needs to work with Paystack payments for African commerce, such as looking up or acting on transactions, and you are comfortable giving it a live secret API key.
- Requirements
- Runs as a local process on the user's machine via the npm package @tracent/paystack-mcp over stdio; desktop only. Requires a Paystack secret API key supplied in the PAYSTACK_SECRET_KEY environment variable, obtained from the Paystack dashboard under Settings and API Keys.
Installation
In SourceWeft
- Open Paystack Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.