Which AI clients work with ISPbox?

Anything that speaks MCP over HTTP: Claude (claude.ai connectors, Claude Desktop, Claude Code), ChatGPT (developer-mode connectors), Cursor, VS Code and most agent frameworks. People sign in with OAuth; scripts use a workspace API key.

Can the AI see everything in my workspace?

No. A connection only receives the scopes granted on the consent screen, further limited by the connecting user's panel permissions. Tools outside those scopes are never listed to the AI.

Can the AI break my billing?

Write access is opt-in per module. Irreversible actions like voiding invoices or reversing payments are marked destructive, so MCP clients require explicit confirmation, and every call lands in the audit log with its arguments.

Is the MCP server included in my plan?

It is included on the Growth and Scale plans - the same entitlement as the REST API. Workspace admins can switch it off entirely at any time.

ISPbox

01 Feature Spotlight

Your ISP Panel, Now Speaks AI

Every ISPbox workspace exposes a Model Context Protocol server. Connect Claude, ChatGPT, Cursor or any MCP client and ask questions your panel can answer - or let AI do the clicking for you.

"Why is John Smith offline?" - one AI question runs a full connectivity diagnosis
Each staff member connects with their own account; AI only gets the permissions they have
Every AI action is audited, destructive actions require explicit confirmation

Create Account View Pricing

app.ispbox.net

ISPbox AI Assistant - built-in MCP server for AI clients

// In the product

Inside the AI assistant

Real screens from the product - the same views your team works in every day.

Connect Claude or any MCP client

ISPbox ships a built-in MCP server with OAuth - connect an AI assistant in minutes, no middleware and no API keys pasted into prompts.

app.ispbox.net

Connecting an AI assistant to ISPbox over MCP

Every AI action audited

Each tool call is logged with who, what and when - AI access is scoped, revocable and reviewable.

app.ispbox.net

AI activity log with every tool call recorded

→ Under the hood

What the AI can do

AI assistants are only as useful as the systems they can reach. ISPbox ships a built-in MCP (Model Context Protocol) server - the open standard used by Claude, ChatGPT and Cursor - so your AI can search customers, diagnose connectivity, read your LibreNMS/Zabbix alerts, notify the customers behind a failing tower, manage tickets and visits, record payments and run every panel report - in the same workspace your team uses, under the same permissions.

Task-shaped tools, not raw API calls

The server exposes about 50 tools designed around real ISP work. The flagship, diagnose-service, answers "why is this customer offline?" by combining service status, billing suspension state, the live RADIUS session and router health into one verdict - the same reasoning a senior tech would do across five screens. Aggregate tools like get-client return profile, services, balance, recent invoices and open tickets in a single call, and get-report runs every panel report (AR aging, billing trend, revenue by location, package mix, churn, top data users) for business questions.

The outage chain: diagnose, target, notify

The tools compose. When your monitoring (LibreNMS or Zabbix, both supported live) reports a tower down, the AI links the alert to the device on your network map, resolves every customer downstream of it and previews the audience. After your explicit approval it sends the outage email or SMS - the same mass-messaging engine the panel uses, with the same placeholders. Planned maintenance works the same way: "warn everyone behind Tower 3 about tomorrow night" is one sentence.

A support agent, not just a dashboard

Beyond reading data, the AI performs the actual support actions: re-send a portal invitation when a customer cannot log in, block or unblock a client with a reason, pause a service for the season, schedule a technician visit on a ticket, check inventory for the ONT the installer needs - and answer "how do I..." questions from the official ISPbox documentation with cited article links.

Per-user OAuth, audit trail and guardrails

Each staff member connects their own AI client by signing in with their ISPbox account - a browser consent screen shows exactly which modules the AI may touch, limited to what that user can already do in the panel. Every tool call is logged with who, what, arguments and duration; workspace admins see the full AI activity feed and hold a kill switch. Destructive actions are annotated so AI clients ask for confirmation, and customer-written text is marked untrusted to resist prompt-injection tricks hidden in ticket bodies.

Works with Ticketing, Billing, Network Monitoring

02 Why this feature matters

Built for high-speed ISP operations

From Outage to Customer Notice in One Chat

A tower goes down. Your AI diagnoses it, sees the 46 customers behind it and drafts the outage message - you approve, it sends. Diagnosis, audience and notification in a single conversation.

It Reads Your Monitoring

Connected LibreNMS or Zabbix? The AI lists live alerts with severity and device, links them to the affected customers, and can acknowledge them with a proper note when you say so.

Answers Without Dashboards

"How much is overdue and how old is it?", "Which plans earn the most?", "Who eats the most data?" - the AI runs the panel's own reports (AR aging, billing trend, package mix and more) on demand.

Safe by Design

AI connections use OAuth sign-in with per-module scopes intersected with the user's panel permissions. Tools a connection cannot use are never even listed, destructive actions require confirmation, and every call is audited.

03 Use cases

Where ISP teams put this to work

Diagnose "customer offline" complaints in one AI question instead of five panel screens.
Warn everyone behind a failing tower or router about the outage - or a planned maintenance window.
Get a morning briefing: NMS alerts, network health, overdue invoices and open tickets.
Record phone payments, open tickets, schedule technician visits and send portal invites by telling the AI what happened.
Ask "how do I configure dunning?" - the AI searches the official docs and cites the article.

// Related

What ISP and WISP teams search for

isp ai assistant mcp server isp connect claude to isp panel ai for isp billing ai isp support isp automation ai

04 FAQ

Frequently asked questions

Which AI clients work with ISPbox?: Anything that speaks MCP over HTTP: Claude (claude.ai connectors, Claude Desktop, Claude Code), ChatGPT (developer-mode connectors), Cursor, VS Code and most agent frameworks. People sign in with OAuth; scripts use a workspace API key.
Can the AI see everything in my workspace?: No. A connection only receives the scopes granted on the consent screen, further limited by the connecting user's panel permissions. Tools outside those scopes are never listed to the AI.
Can the AI break my billing?: Write access is opt-in per module. Irreversible actions like voiding invoices or reversing payments are marked destructive, so MCP clients require explicit confirmation, and every call lands in the audit log with its arguments.
Is the MCP server included in my plan?: It is included on the Growth and Scale plans - the same entitlement as the REST API. Workspace admins can switch it off entirely at any time.

05 Explore more

Related features

All features

Provisioning

Automate ISP service activation: turning a service on writes the PPP secret, DHCP lease and speed queue to the router or RADIUS, plan changes update it in place, and suspension removes or limits it, with audit jobs that check the router against the panel.

Learn more

Inventory

Track ISP equipment from stock to subscriber: ISPbox logs items by serial number, moves them through statuses like in stock, with a tech, in service, maintenance and retired, assigns them to technicians and customer services, and keeps a transfer audit.

Learn more

Work Orders

Coordinate ISP field work in ISPbox: schedule installs and repairs as tickets with a date, an assigned technician and a checklist, and see them on a team calendar, so dispatch, support and field crews work from one place.

Learn more