
Lightbill Mcp Server
io.github.lightnet19Published by GitHub account lightnet19v0.1.1Updated Oct 24, 2026
LightBill ISP billing MCP server: 134 tools (customers, routers, OLT, invoices, payment).
Overview
A local MCP server that connects an assistant to LightBill ISP billing, exposing 134 tools for customers, routers, OLT, invoices and payments.
- What you can do
- Manage customers and their billing records in LightBill ISP billing software, including invoices and payments, through a large set of dedicated tools (134 in total). Work with network equipment records such as routers and OLT devices. The manifest lists no individual tool names, so the exact operations available per area are not documented here.
- When to use it
- Useful when an assistant needs to look up or act on ISP billing data in LightBill — customer accounts, invoices, payments, or router and OLT records — without switching to the LightBill interface.
- Requirements
- Runs as a local process (stdio) installed from the PyPI package lightbill-mcp-server, so a Python environment is needed. Requires a LightBill AI API key supplied through the LIGHTBILL_API_KEY environment variable, sent as the X-AI-Key header. An optional LIGHTBILL_BASE_URL variable sets the API base URL. Desktop only; network access to the LightBill API is required.
Installation
In SourceWeft
- Open Lightbill Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.