NetLicensing MCP Server
Wire your agent into NetLicensing so it can create products, issue keys, and manage customer license lifecycles from the IDE.
Overview
NetLicensing MCP is a MCP server for the Validate phase that exposes NetLicensing REST license lifecycle management to AI coding agents over stdio.
What is this MCP server?
- stdio MCP server (PyPI netlicensing-mcp v0.1.7) against NetLicensing REST v2
- Optional demo credentials when NETLICENSING_API_KEY is empty
- Configurable NETLICENSING_BASE_URL and MCP_TRANSPORT (stdio or http)
- AI-driven license lifecycle operations via MCP tools (create, validate, renew flows)
- Verbose debug toggle via MCP_VERBOSE
- Server schema version 0.1.7
- Default API base https://go.netlicensing.io/core/v2/rest
- Transport modes: stdio (default) or http via MCP_TRANSPORT
What problem does it solve?
Agents cannot safely create or inspect production license records when licensing APIs live outside the repo and copy-paste breaks audit trails.
Who is it for?
Indie developers already on NetLicensing who want agent-assisted license ops during pricing experiments and post-launch support.
Skip if: Teams that only need Stripe subscriptions without node-locked or floating license keys, or builders not ready to operate a licensing backend.
What do I get? / Deliverables
Your agent can call NetLicensing with your API key and manage licenses conversationally while you keep keys in environment variables.
- Registered stdio MCP server talking to NetLicensing REST
- Agent-callable license lifecycle operations against your tenant
- Configurable base URL and transport for local or HTTP deployment
Recommended MCP Servers
Journey fit
Monetization and license rules are proven in Validate before you hard-code billing; this MCP is the integration layer for that decision. Pricing subphase covers license tiers, trials, and entitlement models—the core NetLicensing domain.
How it compares
NetLicensing API integration via MCP, not a Stripe skill or generic CRUD code generator.
Common Questions / FAQ
Who is NetLicensing MCP for?
Solo and small teams shipping licensed software who use NetLicensing and want their coding agent to manage licenses through MCP instead of manual dashboard work.
When should I use NetLicensing MCP?
Use it while defining tiers and entitlements in Validate, and when debugging or extending license flows during Build and early Grow support.
How do I add NetLicensing MCP to my agent?
Install netlicensing-mcp from PyPI, set NETLICENSING_API_KEY and optional NETLICENSING_BASE_URL, add the stdio server entry to Claude Code or Cursor MCP settings, then restart the client.