Cursor
Bring messaging into your coding workflow.
Add to Cursor ↗Open web installer ↗Opens Cursor · confirm, then connect
Open source · Unofficial integration
Your AI client.
Your communication
toolkit.
Connect your Africa’s Talking application to the tools you already use. Check balances, preview messages, and send only when you choose.
Choose your clientNo downloads. No terminal. Connect your account in your browser.
THE CONNECTION
Your AI clientCursor · Claude · ChatGPT · Codex
OAuth + your consent
Africa’s Talking MCPBalance · SMS · Airtime
Your application credentials
Your Africa’s Talking accountSeparate, encrypted connections
SANDBOX FIRSTLIVE WITH CONSENT
✓ No shared provider account✓ Preview before sending✓ MIT licensed
ONE ENDPOINT. YOUR CHOICE.
Where do you want to connect?
Add the hosted server to your client—no local installation required. Your client will ask you to confirm installation and authorize access.
Staging service: connection setup is available. Client compatibility is being verified. Live accounts require separate consent.
Claude
Use your account from a Claude conversation.
Manual setup · your approval
ChatGPT
Connect a custom app to your workspace.
Manual setup · your approval
Codex
Add a remote server to your development tools.
Manual setup · your approval
Connect Cursor
- Click Add to Cursor and allow your browser to open Cursor. Confirm the remote server installation. If the app does not open, use the web installer or copy the MCP URL above.
- Open Cursor settings → Tools & MCP, and add a remote MCP server using this URL. If your version uses JSON configuration, use a server entry with a url field.
- Follow Cursor’s authorization prompt. Check the displayed client and redirect destination before entering your Africa’s Talking credentials.
Installation and authorization require your confirmation. Client compatibility is still being verified.
Connect Claude
- Copy the MCP URL above.
- In Claude, open Customize → Connectors → Add custom connector. Enter a name and the MCP URL. Availability depends on your plan and workspace permissions.
- Choose Connect and follow the authorization prompt. Review each send before allowing it.
Installation and authorization require your confirmation. Client compatibility is still being verified.
Connect ChatGPT
- Copy the MCP URL above.
- In ChatGPT, open Settings → Security and login → Developer mode. Then visit chatgpt.com/plugins to create an app with a name, description, this MCP URL and OAuth authentication. Access depends on your plan and workspace administrator.
- Complete the OAuth connection when prompted. Keep confirmations enabled for tools that send messages or airtime.
Installation and authorization require your confirmation. Client compatibility is still being verified.
Connect Codex
- Copy the MCP URL above.
- Add a remote MCP server in your Codex MCP settings with this URL. CLI users can run: codex mcp add africastalking --url https://at.blackielabs.com/mcp
- Use the client’s login flow (CLI: codex mcp login africastalking), then approve the requested access in your browser.
Installation and authorization require your confirmation. Client compatibility is still being verified.
Remote JSON configuration
For clients that accept an HTTP URL, merge this entry with your existing servers. Your client handles OAuth; no API key belongs in this configuration.
Try your first preview
After connecting, paste this prompt into your client. It does not send a message.
FROM SETUP TO FIRST PREVIEW
Three steps. You stay in control.
01 / ADD YOUR SERVER
Choose your client
Add the remote MCP URL using your client’s settings. Installation always needs your confirmation.
02 / CONNECT YOUR ACCOUNT
Start in the sandbox
Enter your sandbox API key in the secure authorization page—not in chat. A balance check validates access.
03 / REVIEW & APPROVE
Preview your first message
Ask for a dry run first. Sending is optional and requires permission. Sandbox messages reach only the simulator.
BUILT FOR CLEAR BOUNDARIES
Your credentials.
Your connection.
Every authorization creates a separate connection. API keys are encrypted at rest and kept out of MCP tokens. The hosting operator can access runtime credentials; connect only if you trust this service.
Read the security notes ↗What changes between sandbox and live?
Sandbox uses the shared username “sandbox” but your own sandbox key and an isolated connection. It delivers only to the simulator. Live uses your application username and production key, requires an allowed recipient list and explicit opt-in, and charges your Africa’s Talking account.
Can this install without asking me?
No. Clients control installation and authorization. Where official install links are supported, they open a review step. Otherwise, copy the URL and follow the client’s setup instructions.
What permissions am I giving?
Connection setup validates credentials with one balance read. Sending SMS and airtime is optional. Keep per-call approvals enabled in your client. Limits are per connection, not account-wide spending budgets.
How do I disconnect?
Use the at_disconnect tool with explicit confirmation to delete this connection’s stored credential. You can also revoke the client grant. Grant revocation alone does not delete the encrypted credential.
Is this an official Africa’s Talking service?
No. This is an independent, open-source integration. Africa’s Talking and client names belong to their respective owners. Production readiness and client interoperability are still being verified.