Cliqtel AI Access · MCP for Telecom

Give AI agents safe access to your telecom stack.

Cliqtel AI Access exposes numbers, SIP trunks, call flows, and messaging as standard MCP tools. ChatGPT, Claude, Copilot, and your own copilots can search inventory, inspect routing, draft changes, and execute approved actions — without bespoke integrations for each AI host.

Read-first · Approval-gated writes · Tenant-isolated · Audit-logged

▸ claude-desktop → mcp.cliqtel.com
tools/list → 14 tools available
call search_numbers({
country: "NL", type: "mobile",
capabilities: ["sms","voice"]
})
◂ 12 matches · €3.50/mo · ready to draft
call draft_order_number({ number: "+31970..." })
◂ pending user approval → portal
What it is

Your telecom, as tools for AI agents.

Cliqtel AI Access is a remote Model Context Protocol (MCP) server in front of the Cliqtel platform. Every number, trunk, flow, and messaging action becomes a discoverable tool that AI hosts can invoke — with scopes, consent, and audit built in.

🛠️

Tools

Search numbers, create orders, assign DIDs, update SIP targets, draft call flows, send SMS, fetch pricing.

📚

Resources

Country requirements, account inventory, active numbers, connector docs, current routing state, product catalog.

Prompts

Reusable workflows: “Provision a number for a remote office,” “Set up Teams Direct Routing,” “Prepare CCaaS onboarding.”

🔐

Least-privilege scopes

Granular scopes per domain: inventory.read, orders.draft, routing.write, messaging.send.

Approval workflow

Writes land as drafts. Customers approve purchases, route changes, and bulk messaging from the portal or chat.

🧾

Full audit trail

Every tool call, scope grant, and approval stored with actor, client, and result — ready for compliance.

🏷️

Tenant isolation

Access tokens are bound to a single Cliqtel account. No token passthrough, no cross-tenant data access.

🌐

Standards-based

MCP over Streamable HTTP. Works with ChatGPT Responses API, Claude Desktop, Copilot Studio, and custom clients.

How it works

From plug-in to production in four steps.

1

Connect

Add Cliqtel AI Access in the integrations marketplace. Generate a scoped access token.

2

Attach

Paste the mcp.cliqtel.com endpoint into ChatGPT, Claude Desktop, Copilot Studio, or your own MCP client.

3

Inspect

Let the agent search inventory, pricing, call flows, and docs. Read-only by default.

4

Automate

Elevate to draft + approved writes. Agents handle provisioning, routing, and messaging inside guardrails.

Use cases

Operational AI, not chatbot theater.

Provisioning assistant

“Get me a Dutch mobile-capable number for verification traffic and route it to this SIP URI.” Agent searches, validates requirements, drafts the order — you approve.

Admin copilot

“Show all German support DIDs, which queues they terminate on, and where business-hours routing is configured.” Agent reads the call-flow graph and explains it.

Call-flow designer

“Build a business-hours IVR with voicemail fallback and escalation to an on-call queue.” Agent emits a draft flow; you review the diagram and publish.

Partner onboarding

“Generate the 3CX/Asterisk/Teams setup pack for this customer.” Agent returns pre-filled trunk config and step-by-step instructions.

Messaging ops

“Create a WhatsApp-plus-SMS fallback notification setup for this account.” Agent drafts templates and delivery rules for approval.

Regulatory concierge

Agent checks country requirements, flags missing documents, and pre-fills regulatory submissions from account context — you sign off.

Security model

Guardrails built into the protocol.

🎯

Scopes, not keys

Every token carries a specific scope set. A read scope cannot place an order. A draft scope cannot publish.

🧱

No token passthrough

AI hosts get a Cliqtel-issued MCP token, never your upstream carrier or Stripe credentials.

🛎️

Approvals for writes

Irreversible actions — number purchase, route change, live messaging — require explicit approval from an authorized user.

🔍

Full audit trail

Every tool call is logged with caller, client, scopes, arguments, result, and approval decision.

⏱️

Rate limits

Per-scope quotas and token bucket throttling prevent runaway agent loops.

🚫

Revoke on the spot

Rotate or revoke tokens from the portal. Active tool calls are rejected within seconds.

Pricing

Start free. Pay when agents act.

No protocol fees. You pay for the underlying telecom actions agents perform, plus a usage tier for high-volume automation.

Discover
Free
Read-only access for every Cliqtel account.
  • ✓ All read tools & resources
  • ✓ Inventory, pricing, routing, docs
  • ✓ 10,000 tool calls / month
  • ✓ 1 MCP client connection
  • ✓ Full audit log
Start free
Most popular
Automate
€49/mo
Draft + approved writes for growing ops teams.
  • ✓ Everything in Discover
  • ✓ Draft orders, reserved numbers
  • ✓ Call-flow drafting & publishing
  • ✓ Messaging send with approvals
  • ✓ 100,000 tool calls / month
  • ✓ 5 MCP client connections
  • ✓ Approval workflow + email alerts
Request Automate
Embed / OEM
Custom
Partner-branded MCP endpoint on your own domain.
  • ✓ Everything in Automate
  • ✓ Partner-branded MCP domain
  • ✓ Custom tool catalog
  • ✓ Unlimited tool calls
  • ✓ Tenant isolation per customer
  • ✓ SLA + priority support
  • ✓ OAuth 2.1 + dynamic client registration
Talk to sales

Tool-call overages billed at €0.0005 / call. Telecom actions (numbers, messages) billed at standard Cliqtel rates.

Works with

Drop into any MCP-capable host.

ChatGPT & OpenAI Responses

Attach Cliqtel AI Access as a remote MCP server in the Responses API or the ChatGPT connector UI.

Claude Desktop & Claude API

Native MCP support — add the Cliqtel endpoint and Claude discovers every tool, resource, and prompt automatically.

Microsoft Copilot Studio

MCP is generally available in Copilot Studio; paste the endpoint, pick scopes, and expose Cliqtel to your agents.

Custom copilots

Any JSON-RPC or MCP SDK client works. We publish TypeScript and Python samples in the developer portal.

FAQ

Cliqtel AI Access, explained.

What is MCP?
Model Context Protocol is an open standard that lets AI applications connect to external systems through a uniform interface for tools, resources, and prompts. Cliqtel AI Access is an MCP server that exposes our telecom platform to any MCP-capable AI host.
Is this safe? What prevents an AI agent from doing something destructive?
Three layers. Scoped tokens limit what tools an agent can call at all. Destructive and irreversible actions are gated behind an approval workflow — agents can only draft them. Every tool invocation is written to an immutable audit log.
Does the AI get access to my carrier credentials or Stripe keys?
No. The AI host receives a Cliqtel-issued MCP token that only speaks to our platform. Upstream carrier and payment credentials never leave Cliqtel.
Can I use this with my own internal copilot?
Yes. Any MCP-capable client can connect. We publish TypeScript and Python samples, and the OpenAI Responses API supports remote MCP servers directly.
How is this different from your REST API?
The REST API is for developers building apps. MCP is for AI agents discovering and using tools at runtime without bespoke integration code per AI host. Both stay available — MCP sits on top of the same service layer.
What ships first?
The Discover tier is first — read-only tools and resources for inventory, pricing, call flows, SIP config, docs, and regulatory requirements. The Automate tier follows with draft + approved writes.
Can I white-label the MCP endpoint?
Yes, on the Embed / OEM tier. Your MCP server runs under your own domain with a custom tool catalog and tenant isolation per end-customer.
Do I pay for tool calls or for telecom actions?
Both, but most tool calls are free within tier quotas. When an agent actually purchases a number or sends a message, you pay the standard Cliqtel rate for that action — there is no markup for calling it via MCP versus the portal.

Ready to let agents run your telecom ops?

Start on the free Discover tier. No card, no commitment — read-only access for every Cliqtel account.