MCP Server
MCP Server
LicenseSeat's MCP server lets your AI agent set up licensing with you: it reads these docs, checks what your organization has set up, and creates products, license plans and test licenses after you say yes. No tool shows your API keys, emails your customers or touches your payment platform.
Endpoint (Streamable HTTP): https://licenseseat.com/mcp
Connect
- Claude Code:
claude mcp add --transport http licenseseat https://licenseseat.com/mcp, then/mcpto sign in. - Claude (web and desktop): Settings → Connectors → Add custom connector, paste the endpoint, sign in.
- Cursor: add
{"mcpServers": {"licenseseat": {"url": "https://licenseseat.com/mcp"}}}to.cursor/mcp.json, approve the sign-in. - ChatGPT: turn on developer mode, then Settings → Apps & Connectors → Create; paste the endpoint, choose OAuth, sign in.
The first time, you sign in to LicenseSeat and choose one of your organizations. Revoke a client any time in Settings → Connected apps.
What it can do
Start with "What's left to set up?". The agent calls setup_status and walks the checklist: create the product, create its license plans (seats, duration, update coverage, entitlements), issue a test license, wire your app's validate and activate calls with an SDK, and create a draft release.
| Tool | Who |
|---|---|
setup_status, products, license_plans, licenses, license_status, releases, latest_release, signing_key, docs_search, docs_page, openapi |
any member |
product_create, license_plan_create, test_license_create, license_revoke, release_create |
owners and admins |
What stays with you
The agent tells you when a step is yours:
- Your API key. Create the publishable key (
pk_…) in Settings → API keys and paste it into your app yourself. Keys are never shown over MCP. Your app ships only the publishable key; the secret key (sk_…) stays on your server. - Your payment platform. Connect Stripe, Paddle, Gumroad, Lemon Squeezy, Shopify or Polar in Settings so purchases issue licenses; the payment links and webhooks live in that platform's dashboard.
- Signing and stores. Apple certificates, notarization and registry accounts with MFA.
- Uploading and publishing releases. The agent creates the draft; you add the files and publish from the Distribution tab or from CI.
Things your agent will get right
validateanswers HTTP 200 for revoked and expired licenses too: readdata.valid.activatespends a seat: once per device, on first run, not on every start.- The device fingerprint must be byte-identical on every call.
- Revoking a license cannot be undone; to free one seat, deactivate that device.
Access and limits
- Every tool runs as you, in the organization you chose, with your role there. Members and viewers can read; owners and admins can also change the setup.
- Licenses are shown by id, plan, status and seats, never by who owns them. A customer's license key is masked; only test license keys are shown whole.
- 60 tool calls a minute and 2,000 a day per connected client.
- Access tokens last an hour and refresh on their own; revoking in Settings ends access at once.