
NetLicensing MCP Server
io.github.Labs64Published by GitHub account Labs64v0.1.11Updated Nov 7, 2026
Labs64 NetLicensing MCP server for AI-driven software license lifecycle management.
Overview
Local MCP server that connects an assistant to Labs64 NetLicensing for AI-driven software license lifecycle management.
- What you can do
- The manifest lists no tools, so capabilities are known only from the description.
- It connects an assistant to the Labs64 NetLicensing service for software license lifecycle management.
- It runs locally over stdio by default, with an optional HTTP transport mode.
- It can use demo credentials when no API key is supplied, or a real NetLicensing API key and custom base URL.
- When to use it
- Consider it if you manage software licenses on Labs64 NetLicensing and want an assistant to help with license lifecycle tasks. It is a desktop-only local server, so it suits individual developer setups rather than shared or web-hosted use.
- Requirements
- Python package netlicensing-mcp run as a local process over stdio (or HTTP via MCP_TRANSPORT). A NetLicensing account and API key in NETLICENSING_API_KEY for real data; leaving it empty falls back to demo credentials. NETLICENSING_BASE_URL can override the API endpoint, and MCP_VERBOSE enables debug logging.
Installation
In SourceWeft
- Open NetLicensing 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
2- v0.1.11LatestNov 7, 2026
- v0.1.10Sep 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.