Cursor
Bring balances, SMS previews and airtime into your coding workflow.
Africa’s Talking, connected to Cursor. Check your balance, preview a message, and decide when it is ready to send.
Connect CursorNo downloads. No terminal. Connect your account in your browser.
Illustrative preview. Your account connects after authorization.
Add the hosted server to Cursor—no local server required. Confirm installation, then authorize your Africa’s Talking account.
Bring balances, SMS previews and airtime into your coding workflow.
In Cursor’s MCP configuration, merge this entry with your existing servers. Cursor handles OAuth; no API key belongs in this configuration.
After connecting, paste this prompt into Cursor. It does not send a message.
Add the remote MCP URL using Cursor’s settings. Installation always needs your confirmation.
Enter your sandbox API key in the secure authorization page—not in chat. A balance check validates access.
Ask for a dry run first. Sending is optional and requires permission. Sandbox messages reach only the simulator.
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 notesSandbox 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.
No. Cursor controls installation and authorization. The install link opens a review step. If it does not open, copy the server URL into Cursor’s MCP settings.
Connection setup validates credentials with one balance read. Sending SMS and airtime is optional. Keep per-call approvals enabled in Cursor. Limits are per connection, not account-wide spending budgets.
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.
No. This is an independent, open-source integration. Africa’s Talking and client names belong to their respective owners. Production readiness and the full Cursor authorization flow are still being verified.