By afrotools
Integrate African APIs with zero guesswork. Automatically fetches specs, surfaces gotchas, and scaffolds correct implementations for Paycard, LengoPay, NimbaSMS, and more.
Use this skill when the user has a failing or broken Afro.tools integration — wrong status codes, auth errors, webhook not firing, unexpected response fields, or any runtime error from a Paycard, LengoPay, NimbaSMS, or other Afro.tools provider. Activate even if the user just pastes an error without context.
List all available specs in the Afro.tools registry, optionally filtered by category or provider. Manual invocation only.
Scaffold a new ATSS spec (schema.json + canonical_example.ts) for a provider and capability. Manual invocation only.
Use this skill whenever the user wants to integrate, implement, or test a payment API from an African provider — including Paycard, LengoPay, Wave, Djomy, Bictorys, or any provider in the Afro.tools registry. Activate even if the user only says "add payment", "connect to Paycard", or "implement a checkout flow" — always fetch the exact spec before writing any code.
Use this skill whenever the user wants to send SMS messages, OTPs, or bulk notifications via an African SMS provider — including NimbaSMS or any provider in the Afro.tools registry. Activate even for "send a verification code" or "add SMS notifications", not just explicit mentions of a provider name.
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A static registry of structured, machine-readable API specs for African payment and SMS providers. Each spec is a self-contained description of one API capability: what to send, what comes back, what can go wrong, and the gotchas that real integrations surface.
A spec lives at specs/{category}/{provider}/{capability}/ and contains exactly two files:
schema.json — ATSS-compliant description of the API capability (endpoint, auth, input/output schemas, gotchas)canonical_example.ts — TypeScript implementation using native fetch, compiles with tsc --noEmitSee ATSS.md for the full specification.
| Provider | Category | Country | Capabilities | Status |
|---|---|---|---|---|
| Paycard | payment | GN | create_payment, verify_payment, webhook_payment_completed | ✅ Verified |
| LengoPay | payment | GN | create_payment, verify_payment, webhook_payment_completed | ✅ Verified |
| Wave | payment | SN, CI, ML | create_payment, verify_payment, webhook_payment_completed | Planned |
| Djomy | payment | GN | create_payment, verify_payment | Planned |
| Bictorys | payment | — | create_payment, verify_payment, webhook_payment_completed | Planned |
| NimbaSMS | sms | GN | send_otp, send_bulk | Planned |
Add to your MCP client configuration:
claude_desktop_config.json){
"mcpServers": {
"afrotools": {
"type": "http",
"url": "https://mcp.afro.tools/mcp"
}
}
}
{
"mcp": {
"servers": {
"afrotools": {
"type": "http",
"url": "https://mcp.afro.tools/mcp"
}
}
}
}
claude mcp add afrotools --transport http https://mcp.afro.tools/mcp
Or add to your project's .mcp.json:
{
"mcpServers": {
"afrotools": {
"type": "http",
"url": "https://mcp.afro.tools/mcp"
}
}
}
Install the plugin to get Afro.tools skills directly in your editor:
/plugin marketplace add afrotools/afrotools
/plugin install afrotools
The plugin includes:
Auto-activated skills (trigger automatically based on your request):
payment — integrating a payment API → fetches the right spec before writing any codesms — integrating an SMS API → samedebug — debugging a failing integration → cross-checks your code against the spec and gotchasManual commands:
/afrotools:spec <provider> <capability> — inspect the full spec for a provider/capability/afrotools:list — list all available specs with their status/afrotools:new <category> <provider> <capability> — scaffold a new spec (for contributors)If you don't use the plugin, you can copy a single SKILL.md into your project:
plugin/skills/payment/SKILL.md ← for payment integrations
plugin/skills/sms/SKILL.md ← for SMS integrations
Place it in your project's .claude/skills/ directory and Claude Code will pick it up automatically.
See CONTRIBUTING.md to add a spec or improve an existing one.
All specs go through a lifecycle: draft → compliant → verified.
A provider is AI Ready when all its capabilities reach verified.
Apache 2.0 — see LICENSE.
npx claudepluginhub afrotools/afrotools --plugin afrotoolsExpert guidance for integrating Paymob payment gateway. Covers the Intention API for card payments, mobile wallets, BNPLs, Apple Pay, Google Pay, kiosk, and bank installments across all regions. Supports Node.js, Python, PHP, .NET, Ruby, React, Flutter, and native mobile SDKs.
Editorial "Integration & APIs" bundle for Claude Code from Antigravity Awesome Skills.
expert-level payme payment system integration skill for uzbekistan's payme business platform
Pay-per-call access to premium APIs via x402/MPP micropayments.
Expert subagent and skills for implementing the Machine Payments Protocol (MPP) — the open standard co-authored by Stripe and Tempo Labs for HTTP 402-based machine-to-machine payments, enabling AI agents to pay for API calls, data, and services autonomously.
Official Stripe payment platform skills for checkout, billing, Connect, and API upgrades.