By afrotools
Integrate African payment and SMS APIs (Paycard, LengoPay, NimbaSMS, Wave, Djomy, Bictorys) by fetching live specs, inspecting endpoints and gotchas, debugging mismatches, and scaffolding validated provider schemas from documentation URLs.
Use this skill ONLY when the user has a failing integration that is specifically based on an Afro.tools spec — the user is integrating a provider whose spec exists in the Afro.tools registry (Paycard, LengoPay, Djomy, Wave, NimbaSMS, etc.) and encounters wrong status codes, auth errors, webhook failures, unexpected response fields, or runtime errors. Do NOT activate for generic debugging, non-afrotools providers, or integrations not based on an Afro.tools spec. This skill diagnoses whether the problem is a spec error, a missing gotcha, or an undocumented API change.
List all available specs in the Afro.tools registry, optionally filtered by category or provider. Manual invocation only.
Use when adding a new API provider to the Afro.tools registry. Point it at the provider's documentation URL (or a local file) and it will: discover all API endpoints, create provider.json, generate schema.json + canonical_example.ts for every capability, run validation, and optionally verify response schemas against the live API. Invoke with: /afrotools:new <docs_url> [category] [provider_slug]. 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.
Integrate Wave, Paycard, and any African API in a single prompt.
African APIs are production-grade. What's been missing is a standard, machine-readable format that AI agents can consume directly — without parsing documentation pages or guessing at request shapes.
Afro.tools fills that gap: a static, open-source registry of structured specs for African APIs. Each spec is verified against the live API and exposes exactly what an AI agent needs to generate correct integration code on the first try.
graph LR
A["specs/ — open source"] -->|GitHub raw URLs| B["MCP server\nmcp.afro.tools"]
B -->|MCP protocol| C["AI agent\nClaude · Cursor · Copilot · ..."]
C -->|generates| D["Integration code\nin your app"]
A -->|plugin| C
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 --noEmitEach provider also has a provider.json at the root of its folder:
specs/payment/paycard/
├── provider.json ← metadata + description + example_prompt
├── create_payment/
│ ├── schema.json
│ └── canonical_example.ts
├── verify_payment/
└── webhook_payment_completed/
See ATSS.md for the full specification.
| Provider | Category | Country | Capabilities | Status |
|---|---|---|---|---|
| Paycard | payment | 🇬🇳 | 3 | ✅ AI Ready |
| Djomy | payment | 🇬🇳 | 7 | 4 verified · 3 ready |
| LengoPay | payment | 🇬🇳 | 8 | 2 verified · 6 ready |
| NimbaSMS | sms | 🇬🇳 | 11 | 📋 Ready |
| Orange Money Mali | payment | 🇲🇱 | 2 | 📋 Ready |
| Wave | payment | 🇸🇳 🇨🇮 🇲🇱 +8 | 12 | 📋 Ready |
Legend: ✅ AI Ready = all capabilities verified · X verified · Y ready = awaiting production validation · 📋 Ready = spec validated · 🗓 Planned = specs coming soon
claude mcp add --transport http afrotools https://mcp.afro.tools/mcp
{
"mcpServers": {
"afrotools": {
"type": "http",
"url": "https://mcp.afro.tools/mcp"
}
}
}
/plugin marketplace add afrotools/afrotools
/plugin install afrotools
Auto-activated skills based on context:
payment — integrating a payment APIsms — integrating an SMS APIdebug — when an integration based on an afrotools spec fails → diagnoses whether the problem is a spec error, a missing gotcha, or an undocumented API changeManual commands:
/afrotools:spec <provider> <capability> — inspect a full spec/afrotools:list — list all available specs/afrotools:new <category> <provider> <capability> — scaffold a new specSee CONTRIBUTING.md to add a spec or improve an existing one.
Spec lifecycle: draft → ready → verified
A provider earns the AI Ready badge when all its capabilities reach verified.
Apache 2.0 — see LICENSE.
npx claudepluginhub afrotools/afrotools --plugin afrotoolsEditorial "Integration & APIs" bundle for Claude Code from Antigravity Awesome Skills.
Browse and buy gift cards, mobile top-ups, and eSIMs on Bitrefill — 1,500+ brands, 180+ countries, crypto/x402/balance payments
Expert, workflow-driven guidance for integrating the Paymob payment gateway across Egypt, UAE, KSA, and Oman. Routes by platform (Shopify apps / prebuilt e-commerce plugins vs custom build), onboarding, web/API (Intention API + Unified Checkout + Pixel SDK), and native Mobile SDKs. Covers all 3 HMAC types (transaction, card token, subscription), transaction inquiry/reconciliation, subscriptions, saved cards (CIT/MIT), Auth/Capture, refunds/void, split features, and convenience fees, and ships corrected ready-to-use code for Node.js, Python, PHP, .NET, Ruby, and frontend. Bundles Paymob's official MCP server for live account actions. Triggers even when no provider is named for a regional payment request.
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.
expert-level payme payment system integration skill for uzbekistan's payme business platform