The Simple Telecom MCP Server
Connect AI assistants like Claude, Cursor or VS Code to your Simple Telecom account through the Model Context Protocol — read-only insight and human-approved changes, with cancellation and payments impossible by design. Coming soon.
Frequently Asked Questions
What is MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools and data. Instead of copy-pasting between your assistant and your console, the assistant calls the Simple Telecom tools directly — with the scopes and approvals described on this page.
Which AI assistants will work with it?
Any MCP client that supports custom headers — popular options include Claude Desktop, Claude Code, Cursor and VS Code. The console will show a copy-paste configuration with the endpoint and client IDs filled in.
Can an AI assistant cancel my number or move my service?
No — by design. The MCP server exposes no cancellation, closure or transfer-out tools, and no payment scope. Cancelling a service or transferring a number stays browser-only, owner-only, with fresh multi-factor authentication.
Can an assistant approve its own changes?
No. An assistant can prepare a change, which produces a bound preview that expires after five minutes. Applying it requires an approval reference issued to a human through the platform — an assistant cannot self-approve.
Do I need to write code to use it?
No. If you can paste a configuration block into your AI assistant settings, you can connect it. Writing code is only needed if you are building your own automation on top of the underlying API.
When will the MCP server be available?
It is coming soon — it is in final development now. Availability will be announced on the API changelog page, and this page will be updated the day it goes live.
Status: coming soon. The Simple Telecom MCP server is in final development. This page describes exactly what it will do, taken from the product specification. We publish it now so you can plan integrations — and we will update it the day the feature goes live. Watch the API changelog for the announcement.
What the Simple Telecom MCP server does
The Model Context Protocol is the open standard that connects AI assistants to real tools and data. The Simple Telecom MCP server applies it to your phone account: your assistant can read your services and call records, read and draft configuration changes, and walk your team through onboarding — while the platform enforces hard boundaries on everything that touches money, membership or the life of your service.
It sits on top of the same capabilities as the Simple Telecom REST API, so everything your assistant can do is scoped, logged and approval-bound.
The tool set
The server exposes a deliberately small, closed set of tools:
Onboarding
| Tool | What it does |
|---|---|
| read_onboarding_status | See where a sign-up or activation is up to |
| save_onboarding_details | Fill in your business details during sign-up |
| select_offer | Choose a plan from your available options |
| create_card_handoff | Start a secure, platform-handled payment-card flow (card details never pass through the assistant) |
| prepare_service / confirm_service | Stage a new service, then activate it after platform approval |
Services & configuration
| Tool | What it does |
|---|---|
| read_services | List your active services and their numbers |
| read_current_configs | Read how each service is configured today |
| save_current_configs | Save configuration changes (within your granted scopes) |
| prepare_service_change / confirm_service_change | Stage a change with a bound preview, then apply it after approval |
| read_config_snapshots | See the configuration history for audit and rollback |
Usage
| Tool | What it does |
|---|---|
| read_call_records | Pull rated call records — the same data behind your invoices |
The set is closed: there is no generic execute endpoint, and tools that are not listed here do not exist. Each call runs under a per-call grant binding, so every action is tied to the identity, account, client and grant that made it.
Safety by design
This is the part most MCP integrations get wrong, so we built it in from day one:
- No life-of-service tools. There is no way to cancel a service, close an account, surrender a number or transfer it out through MCP — or through the API at all. Those actions stay in the browser, owner-only, with fresh multi-factor authentication.
- No payment authority. Card capture happens in a platform-handled flow; card details never pass through the assistant. There is no scope that charges money.
- Prepare, then a human confirms.
prepare_*tools return a bound preview — account, configuration, quote digest — that expires after five minutes. Applying it needs an approval reference issued to a person through the platform. An assistant cannot setapproved: trueand call it done. - Scoped tokens. Every connection runs on the scopes and roles model — a viewer-scoped token gets read-only answers, full stop.
How connection will work
- Create a token — the account owner creates a personal access token in the console and chooses its scopes.
- Copy the configuration — the console Integrations page shows your MCP endpoint and client IDs in a copy-paste configuration block. The config contains endpoint and client IDs only — never a token.
- Paste it into your assistant — any MCP client that supports custom headers works: Claude Desktop, Claude Code, Cursor, VS Code and similar.
- Work scoped — the assistant can now read what your scopes allow and prepare changes for approval.
One warning we feel strongly about: do not route your token through third-party hosted key proxies. The token is the key to your account — keep it in your own client configuration, and rotate or revoke it the moment anything looks off.
Who is it for?
- Owners who live in an AI assistant — "how many calls did we miss yesterday?" answered from real rated records, not a guess.
- Technical operators — let your assistant watch configuration drift and draft corrections you approve in one click.
- Agencies managing client numbers — scoped tokens mean an assistant sees only what the scope allows.
More scenarios: API use cases.
Availability
Coming soon — in final development now. The API changelog records the launch, and this page gets its final update the day the feature goes live. Questions in the meantime: info@simpletelecom.com.au.