Netlicensing
Manage NetLicensing products, license modules, and customer agreements from your agent while wiring licensing into a shipped desktop, CLI, or SaaS product.
Overview
com.mcparmory/netlicensing is a MCP server for the Build phase that creates and manages NetLicensing products, modules, licenses, and customer agreements through agent tools.
What is this MCP server?
- Create and manage software licenses and licensing modules via MCP tools
- Define products and tie modules to commercial offerings
- Handle customer licensing agreements without a separate admin-only session
- stdio MCP with uvx (mcparmory-netlicensing 1.0.2) or Docker OCI packaging
- Suited to indie desktop, CLI, and API products that use NetLicensing as the authority
- Server version 1.0.2
- 2 transport packages: PyPI uvx and OCI Docker
- stdio MCP transport
Community signal: 25 GitHub stars.
What problem does it solve?
Toggling between your repo and a licensing console slows you down when every new SKU or customer fix needs both code and entitlement updates.
Who is it for?
Indie developers already on NetLicensing who want agent-driven license and product maintenance during feature and packaging work.
Skip if: Builders using Stripe-only subscriptions with no NetLicensing stack, or teams that need a full billing storefront instead of licensing API tools.
What do I get? / Deliverables
After registration, your agent can perform NetLicensing administration alongside implementation so licensing stays synchronized with what you ship.
- Agent-driven creation and updates of licenses and licensing modules
- Product and module definitions aligned with your commercial packaging
- Customer agreement operations callable from development workflows
Recommended MCP Servers
Journey fit
License products and customer entitlements are product infrastructure you integrate during Build, before you rely on them in Ship and Operate. NetLicensing is an external licensing API; the integrations subphase is where solo builders connect third-party entitlement systems into their codebase and ops scripts.
How it compares
MCP entitlement admin for NetLicensing, not a payment gateway or generic CRM skill.
Common Questions / FAQ
Who is com.mcparmory/netlicensing for?
Solo builders and small teams shipping licensed software who use NetLicensing and want MCP tools for products, modules, licenses, and customer agreements.
When should I use com.mcparmory/netlicensing?
Use it while building or extending licensing integration—adding modules, SKUs, or customer keys—before and after launch when entitlements must match your codebase.
How do I add com.mcparmory/netlicensing to my agent?
Configure stdio MCP with uvx mcparmory-netlicensing 1.0.2 or ghcr.io/mcparmory/netlicensing:1.0.2, and supply NetLicensing API credentials in the environment your agent documents.