SIMcloud MCP · Connect your AI
Buy prepaid electricity, Takealot and Checkers vouchers, airtime and data from a compatible AI assistant. Connect your SIMcloud account, ask for what you need and confirm the purchase.
Reporting cannot spend. Transaction access can place orders from your wallet.
New to SIMcloud? Create your account or view pricing.
“Get me a R100 Checkers voucher. Show me the details before you buy.”
list_vas_productscreate_vas_orderYour AI checks the product and price. You confirm the purchase before it places the order through your SIMcloud account.
About SIMcloud MCP
SIMcloud MCP lets you buy prepaid electricity, Takealot and Checkers vouchers, airtime and data through a compatible AI assistant. It connects the assistant to your SIMcloud account and wallet using the Model Context Protocol. Your AI client can read your current wallet balance, transaction history and order status. Transaction access also allows it to submit supported prepaid orders and SMS messages.
It is built for South African prepaid workflows: helping a field team stay connected, checking a customer recharge, buying supported electricity, fulfilling rewards or reviewing account activity. Airtime and data workflows cover Vodacom, MTN, Cell C and Telkom.
SIMcloud manages your account, wallet, product access and order processing. You sign in on SIMcloud and choose which permission to grant.
You can also speak your request. Use voice input where your AI app supports it. If it supports connected tools in a voice conversation, you can ask there too, then review and approve the purchase on screen. Voice and tool availability depend on the app you use.
Access options
Choose reporting when you only need account information. Choose transactions when the workflow needs to place orders or send messages. Each connection has its own server URL and OAuth permission.
Check wallet balance, transaction history and the status of existing airtime, data, SMS, electricity and voucher orders.
reports:read.Read reports, look up products and networks, place prepaid orders, send SMS and create client accounts through the supported tools.
api.Choose your client
Follow the guide for the AI client you use. The guides include the exact server URL, configuration, browser sign-in and a read-only first request.
Connect from the Codex CLI, desktop app or Codex extension for your editor.
Configure SIMcloud as a remote HTTP MCP server in your editor.
Use GitHub Copilot in VS Code with SIMcloud reporting and transaction tools.
Connect Google Antigravity CLI to your SIMcloud account.
Connect Gemini CLI using a paid Gemini API key or an eligible enterprise account.
Use SIMcloud reporting and transaction tools from Claude Code in your terminal.
Connect your editor or Cursor CLI to your SIMcloud account.
Use ChatGPT to check your SIMcloud balance, transaction history and existing orders with reporting-only access.
Client names and logos belong to their respective owners. Codex is an OpenAI product. The GitHub Copilot guide uses VS Code. The Codex extension uses the Codex guide.
Examples
Start by asking for information. For a purchase, let your AI prepare the details, review them, then explicitly confirm the action.
“Show my airtime and data transactions for last week, grouped by service. Include pending and failed orders.”
The AI reads your transaction history and follows additional result pages when needed. For an individual order, it uses the matching status tool. History requests cover at most 90 days at a time.
“Find the current data bundles for this team member’s network. Show me the product and price before placing an order.”
The AI checks the network when unknown and lists available data products. You confirm the recipient, product, amount and reference before it submits a recharge. For larger scheduled or CSV workflows, use the SIMcloud bulk data tools or API.
“Check whether this prepaid meter is supported. Prepare an electricity purchase and show the details for approval.”
The AI checks meter support before ordering, then queries the submitted order using its returned identifier or original reference. Transaction access is needed to buy and retrieve the resulting electricity information.
“Show the available voucher products for this reward. Wait for me to confirm the product, amount and reference.”
The AI lists current voucher products before an order. For an SMS, review the final recipient and message before sending, then check the message status. See the voucher API guide and SMS guide for integration details.
Available tools
Reporting exposes the seven account-read tools below. The transaction connection includes those reads and the additional lookup, product and action tools.
| Service | Reporting tools | Additional transaction tools |
|---|---|---|
| Account | get_wallet_balanceget_transaction_history | register_simcloud_user |
| Airtime and networks | get_airtime_order | lookup_networkcreate_airtime_order |
| Mobile data | get_data_order | list_data_productscreate_data_order |
| SMS | get_sms_status | send_sms |
| Digital vouchers | get_vas_order | list_vas_productscreate_vas_order |
| Prepaid electricity | get_electricity_order | check_electricity_metercreate_electricity_order |
Reporting results exclude redemption secrets. Account registration creates a client account under the connected account and requires that person’s consent. The developer reference and OpenAPI contract describe the supported fields and responses.
Account access and purchases
Sign in on simcloud.co.za, review the permission, and keep your client’s approval prompts enabled. Passwords, OTPs and API tokens do not belong in a chat.
Manage Connected AppsUse a live network lookup, product list or meter check where the service requires it. Confirm the recipient or meter, product, amount and reference.
An accepted or queued response is a processing step. Use the matching order or SMS status tool to follow the outcome.
If a create request times out, query its original order or reference. Do not automatically submit the purchase again while its outcome is unknown.
For developers and integration teams
SIMcloud MCP provides the tool definitions and OAuth connection an AI client needs. The REST API provides direct control over requests, polling and integration logic.
Use remote HTTP MCP and browser-based OAuth. SIMcloud hosts the server. Clients discover the tools, request permission and invoke them against the connected account.
Reporting: https://simcloud.co.za/api/reporting-mcp.php
Transactions: https://simcloud.co.za/api/mcp.php
OAuth uses PKCE with S256. The selected endpoint determines the account permission: reports:read or api.
Use the REST API for an application, scheduled fulfilment, rewards platform or internal system. Store credentials securely, retain order references and implement status polling and explicit error handling.
API documentation · OpenAPI specification · AI integration reference
Current balances, products, prices, networks and meter support come from live requests. Treat documentation examples as setup guidance rather than live account data.
Connection diagram
Your AI client sends a named tool request. SIMcloud checks the connected account and its permission, performs the supported request and returns the result.
OAuth gives your client an access token for reporting or transactions. Tool calls use that token; your password stays on SIMcloud.
You ask for a report or confirm an action.
Checks your account, permission and tool inputs.
Reads account records or processes the approved prepaid request.
Account information, order identifiers and status return to your AI client.
Example agent workflow
A staff member requests a data bundle. An n8n AI Agent can use SIMcloud tools to prepare the recharge, route the purchase for human approval and record the outcome.
Chat Trigger or an internal request form
AI Agent + SIMcloud lookup and product tools
Show the recipient, bundle, price and reference
Call create_data_order after approval
Query get_data_order and save the outcome
Approval declined
End the request without placing an order.
Queued or pending
Wait and query the existing order.
Submission timed out
Reconcile the original reference before any retry.
Attach an MCP Client Tool to the n8n AI Agent. Select Streamable HTTP, use https://simcloud.co.za/api/mcp.php and store your SIMcloud API token in an n8n Bearer Auth credential.
Use Tools to Include → Selected. The preparation node needs get_wallet_balance, lookup_network, list_data_products and get_data_order. Put create_data_order in a separate MCP Client Tool behind human review. Keep credentials out of prompts and request forms.
Separate preparation from purchasing. Require n8n’s human review before the purchase tool can run, show the exact order details and preserve the approved reference and returned identifier in your own records.
Use bounded status checks for queued orders. Route unresolved outcomes to an operator, and do not enable an automatic retry on the purchase step. For a fixed schedule with no AI decision, Node-RED HTTP Request nodes can call the SIMcloud data API directly.
Implementation references: n8n MCP Client Tool · n8n human review for tools · SIMcloud transaction setup.
Help
SIMcloud MCP is a hosted Model Context Protocol server that connects compatible AI clients to your SIMcloud account. It exposes named tools for account reports, South African airtime and data recharges, SMS, prepaid electricity and supported digital vouchers. You choose reporting-only or transaction access when connecting.
Yes. Add the SIMcloud server URL in a compatible MCP client and complete the SIMcloud browser sign-in. You do not need to host a local SIMcloud server or build a REST integration to use these tools. Developers can also use the underlying REST API for applications and scheduled workflows.
No. The reporting endpoint has seven read-only tools. It cannot buy products, send messages, register accounts, change your account, or return electricity tokens and voucher PINs. Transaction access uses a separate endpoint and the api permission.
SIMcloud supports airtime and data workflows across Vodacom, MTN, Cell C and Telkom, plus SMS, supported prepaid electricity meters and available digital voucher products. Product availability, network results and meter support must be checked using the relevant live tools before ordering.
You need sufficient wallet funds for purchases and chargeable services. Reporting access can be used to check your existing account information. Review current product prices and applicable fees before confirming a transaction; your AI client subscription is separate from SIMcloud service charges.
No. A queued or pending response means processing has not reached a confirmed final outcome. Keep the returned order or request identifier and query that existing order. If a create request times out, check its original reference before submitting another purchase.
Yes. Open SIMcloud Connected Apps and revoke the connection. This stops its authorised future access. Revocation does not cancel orders already submitted or remove existing account records. Removing a server from an editor alone does not revoke the SIMcloud authorisation.
MCP suits workflows initiated through an AI client. For a fixed application workflow, scheduled recharge process or tightly controlled integration, use the SIMcloud REST API and its documented request, status and error handling. Both use your SIMcloud account; choose the interface that fits the workflow.
The setup guides cover Codex, Visual Studio Code, GitHub Copilot in VS Code, Claude Code, Cursor, Google Antigravity CLI and Gemini CLI, plus reporting-only access in ChatGPT. Choose the guide for your client and the access you need. Your client account and organisation policies determine whether external tools are available.
VS Code stores the MCP server configuration. GitHub Copilot is an AI assistant that can call those tools from VS Code chat. The Codex extension uses Codex’s own MCP configuration, so it follows the separate Codex guide.
Google Antigravity CLI is the current option for personal Google-account access. Gemini CLI remains available with paid Gemini API keys and eligible Code Assist Standard or Enterprise accounts. Both have separate SIMcloud setup instructions because their configuration files differ.
No. SIMcloud hosts both MCP endpoints. Your client connects over HTTPS using remote HTTP MCP. You configure the server URL and sign in; no local SIMcloud server, Docker container or API proxy is required.
Yes. Authorise each client separately and choose its access level. You can use reporting in one client and transaction access in another. Review the connections in Connected Apps and revoke any you no longer use.
You can use your AI app’s voice input to ask for the same services. If the app supports connected tools during voice conversations, you can speak your request there, then review and approve the purchase on screen. Voice and tool availability depend on your AI app and account.
Yes. An authorised operator can check available services, confirm the staff member’s number and product, then submit a recharge. For a team, retain each person’s request and order reference, require approval before purchases and check the final order status.
An agent workflow platform needs an MCP client that supports SIMcloud’s remote HTTP connection and authentication. n8n provides an MCP Client Tool for AI agents. Node-RED can also call the underlying SIMcloud REST API through HTTP Request nodes when the workflow does not need an AI agent.
Yes. With transaction access, your AI can list the available Takealot and Checkers voucher products, show the current denomination and price, and place the order after you confirm. Product availability and denominations are checked live before the purchase.
The full transaction MCP endpoint accepts an existing SIMcloud API bearer token as well as OAuth. The reporting endpoint requires OAuth. Store API tokens in your client or workflow platform’s credential settings, and never paste them into prompts or public configuration files.
History results are paginated. Ask your client to follow the returned cursor until there are no more results for the requested period. Each history request supports a date range of at most 90 days; split longer reports into smaller periods.
Keep the original order identifier or reference and check its status. A timeout does not prove that the purchase failed. Do not automatically submit the same purchase again while its outcome is uncertain. Contact SIMcloud support if the status cannot be resolved.
Setup guides
Start with a wallet balance request. Choose reporting for account information, or transactions to place orders and send SMS.
Need help? customercare@freepaid.co.za · Privacy notice · Account terms