An unofficial Africa’s Talking integration

Send from the place
you build.

Africa’s Talking, connected to Cursor. Check your balance, preview a message, and decide when it is ready to send.

Connect Cursor

No downloads. No terminal. Connect your account in your browser.

Inside CursorExample workflow
You askPreview an SMS saying “Hello from my app.” Don’t send it yet.

Your message, ready for review.

MessageHello from my app.
EnvironmentSandbox
ActionPreview only
No message has been sent.

Illustrative preview. Your account connects after authorization.

✓ No shared provider account✓ Preview before sending✓ MIT licensed
Get connected

Connect your account to Cursor.

Add the hosted server to Cursor—no local server required. Confirm installation, then authorize your Africa’s Talking account.

Staging service: connection setup is available. The Cursor authorization flow is being verified. Live accounts require separate consent.
Remote JSON configuration

In Cursor’s MCP configuration, merge this entry with your existing servers. Cursor handles OAuth; no API key belongs in this configuration.

Try your first preview

After connecting, paste this prompt into Cursor. It does not send a message.

Setup to first preview

Three steps. You stay in control.

1. Add the server

Connect Cursor

Add the remote MCP URL using Cursor’s settings. Installation always needs your confirmation.

2. 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.

3. Review and approve

Preview your first message

Ask for a dry run first. Sending is optional and requires permission. Sandbox messages reach only the simulator.

Your connection, explained

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. 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.

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 Cursor. 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 the full Cursor authorization flow are still being verified.