Developers
ISPbox MCP Server
Every ISPbox workspace exposes a remote Model Context Protocol server. Connect Claude, ChatGPT, Cursor, Claude Code or any MCP-capable client and let AI work your panel: look up customers, answer "why is this client offline?", manage tickets, record payments and pull billing summaries - always limited to the permissions you grant, with every tool call audited.
Endpoint
https://<workspace>.ispbox.net/mcpTransport: Streamable HTTP (POST, with SSE streaming). The endpoint requires authentication.
Authentication
1. Sign in with your ISPbox account (OAuth 2.1)
For people. Add the endpoint to your AI client and it opens a browser window to sign in and approve access. Only permissions your staff account already has can be granted, and you can revoke a connection anytime under My Account > AI Assistant. Discovery, dynamic client registration and PKCE are supported, so clients like Claude and ChatGPT connect with just the URL.
2. Workspace API key
For automations. Create a key under Settings > API and send it as
Authorization: Bearer ispbx_....
The key's scopes decide which tools are visible.
claude mcp add ispbox --transport http https://<workspace>.ispbox.net/mcp \
--header "Authorization: Bearer ispbx_..."Tools
Tools are task-shaped and scope-gated: a connection only sees the tools its scopes allow.
| Tool | Scope | What it does |
|---|---|---|
search-clients |
clients.read |
Find clients by name, email, phone or account number. |
get-client |
clients.read |
Full client overview: profile, services, balance, recent invoices, open tickets. |
create-client / update-client / add-client-note |
clients.write |
Create and update clients, add internal notes. |
list-services / get-service |
services.read |
Services with package, billing dates and connection details. |
diagnose-service |
services.read |
"Why is this customer offline?" - service status + billing suspension + RADIUS session + router health with a verdict. |
create-service / update-service |
services.write |
Subscribe a client to a package, change status or billing dates. |
get-service-usage / list-sessions / get-network-status |
network.read |
Data usage, live sessions, router health and open incidents. |
list-packages |
packages.read |
Plans with pricing, speeds and billing intervals. |
list-invoices / get-invoice / list-payments / get-client-balance / get-billing-summary |
billing.read |
Receivables, payments, balances and monthly billing snapshots. |
record-payment / create-invoice |
billing.write |
Record manual payments, create one-off invoices. |
void-invoice / reverse-payment |
billing.write |
Destructive accounting actions - MCP clients ask for confirmation. |
list-tickets / get-ticket |
tickets.read |
Ticket queues and full comment threads. |
create-ticket / reply-to-ticket / update-ticket |
tickets.write |
Open tickets, reply (internal or customer-visible), change status. |
list-leads / create-lead / convert-lead |
leads.* |
Sales pipeline: list, create and convert leads to clients. |
The server also ships prompts (daily-briefing,
diagnose-client-connectivity, collections-review)
and an ispbox-guide resource that teaches the AI the recommended flows.
Security model
- OAuth connections are bound to a staff user; granted scopes are re-checked against the user's current panel permissions on every request.
- Tools a connection cannot use are not just blocked - they are never listed.
- Destructive tools (void invoice, reverse payment) are annotated so MCP clients require explicit confirmation.
- Customer-authored text (ticket bodies, notes) is delimited as untrusted content to resist prompt injection.
- Every tool call is logged with actor, arguments, result and duration - visible to workspace admins, next to a workspace-wide kill switch.
Availability
The MCP server is included on the Growth and Scale plans (same entitlement as the REST API). Also see the REST API reference.
