mcp-ispkeeper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ISPKEEPER_API_KEY | Yes | ISPKeeper API key (x-api-key header) | |
| ISPKEEPER_BASE_URL | No | Base URL of your ISPKeeper instance | https://api.anatod.ar |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_clientsB | Search and list ISPKeeper clients with filters. Supports text search, date range, tax status, and more. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_clientA | Get detailed information about a specific client. Use include to get change log, payment commitments, or attached files. Use relaciones to expand connections (coninter,contv,contel,consus for internet/TV/phone/subscriptions). ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_clients_summaryA | Get a quick summary of total and active client counts. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_client_servicesC | Get services for a specific client: invoices, collections, tickets, additionals, internet/TV/phone connections, or subscriptions. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_clients_logB | List change history logs across all clients. Returns database record snapshots before modifications with timestamps and users. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_invoicesA | List invoices with filters by date, type, point of sale. Types: FA,FB,FX (invoices), CA,CB,CX (credit notes), DA,DB,DX (debit notes). ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_invoiceA | Get detailed information about a specific invoice, including items, consolidated data, or PDF print link. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_collectionsB | List payment collections with filters by date and user. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_collectionA | Get details of a specific collection/payment, optionally with consolidated data. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_internet_connectionsA | List internet service connections with filters. tecnologia matches the connection's conexion_tipo code. The docs list R=Radio, T=Torre, O=ONU, H=HFC, S=Switch, P=PPPoE, D=DHCP, but instances use their own set (e.g. H, S, Q, U) — check conexion_tipo on existing records before filtering. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_internet_connectionA | Get detailed information about a specific internet connection, or its change log. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_internet_connections_logB | List change history logs across all internet connections with date filters. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_tv_connectionsA | List TV service connections with filters by client, date, and status. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_tv_connectionA | Get detailed information about a specific TV connection, or its DirecTV Go account data. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_phone_connectionsA | List phone/telephony service connections (includes SSMovil mobile). Filter by client, date, cut-off status. Plans with telefonia_plan_movil=Y are mobile/SSMovil. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_phone_connectionA | Get detailed information about a specific phone/telephony connection (includes SSMovil mobile), or live line data from the Imowi mobile platform. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_subscriptionsA | List subscription services (e.g. SS Seguridad alarm monitoring) with filters by client, plan, subcategory, date, and active status. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_subscriptionB | Get detailed information about a specific subscription service. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_subscription_catalogB | List the subscription catalog: plans, categories, or subcategories. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_ticketsB | List support tickets with filters by date, category, and status. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_ticketA | Get detailed information about a support ticket, optionally with photos, movement log, checkin/checkout, materials used, or chat messages and files. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_tickets_logA | List ticket activity logs across all tickets. Returns movement/change history with timestamps and users. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_network_statusB | Get current network status, optionally filtered by outage date range. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_plansA | List available internet plans, with optional filters for deleted or discontinued plans. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_fttx_infrastructureA | Query FTTx fiber infrastructure: backbones, PONs, NAP boxes, ports, and seals. Use resource_type to select what to list. Use parent_id to drill down the hierarchy (backbone→PONs→boxes→ports) and q for text search. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_fttx_traceA | Trace a FTTx element upward through the hierarchy. Get the full chain: port→box→PON→backbone. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_suppliersB | List suppliers (proveedores) with filters by text, locality, VAT type, and deleted status. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_supplierC | Get detailed information about a specific supplier. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_supplier_invoicesA | List supplier invoices (facturas de proveedores) with filters by date, point of sale, voided and deleted status. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_supplier_invoiceA | Get a specific supplier invoice, or its tax lines. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| list_auxiliary_dataB | List auxiliary/reference data: localities, branches, users, warehouses, categories, payment methods, ticket metadata, and more. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
| get_network_elementA | Get details of a specific element by type and ID: node, subnode, VLAN, SVLAN, user, branch, warehouse, additional, payment method, or ticket category/subcategory/status. ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 32 tools
Tools are largely distinct by entity and action (subscriptions, tickets, invoices, connections, suppliers), and the list/get/search pairing is clear. Some overlap exists among reference-data tools like list_subscription_catalog, list_plans, list_auxiliary_data, and get_network_element, but their descriptions provide enough context to disambiguate.
Almost every tool follows a predictable list_<plural> / get_<singular> / search_<noun> pattern, with consistent pairing across domains. Minor exceptions like get_clients_summary and get_fttx_trace do not undermine the overall convention.
32 tools is heavy for an MCP server, but the broad ISP domain (clients, billing, network, tickets, suppliers) justifies most of them. The surface is larger than ideal and some reference-data tools could be consolidated.
As a read-only query surface it covers most core entities well, including clients, services, billing, tickets, network infrastructure, and suppliers. However, there is no way to enumerate some network elements like nodes/VLANs despite get_network_element existing, and no write or lifecycle operations are available, limiting end-to-end workflows.