MCP
Planned
Plug your AI assistant into your licensing
OwnLicense plans an MCP (Model Context Protocol) server so assistants like Claude, ChatGPT, Cursor or VS Code can use its tools directly: at three levels, each with its own data and its own place to live.
Planned: none of these MCP servers exists yet.
Three levels
1. Docs and integration
Public, in the central service
Helps your assistant integrate licensing into your app: reads the guide and the API, generates the activate and renew code in your language, checks a sample token and explains errors like invalid_key or seats_exhausted.
- “Add license activation to my Swift app.”
- “Why does activate return seats_exhausted?”
No personal data2. Your service account
Central service, signed in
Ask about your aggregated stats, the state of your Workers, alerts and new releases.
- “How many Mac activations did I get yesterday?”
- “Is there a security patch pending?”
Counts only, like the central dashboard3. Administration in your Worker
Your Worker, in your Cloudflare
Support from your assistant: find a license or a customer, see their devices, free one up, resend a key, extend or revoke a license, create a coupon, check sales.
- “Free up the oldest device on ana@example.com's license.”
- “Resend the key for order 1042.”
Personal data: that's why it lives in your account and only you can turn it on
What data each level touches
| Level | Where it runs | What it can read | Your customers' personal data |
|---|---|---|---|
| Docs and integration | Central service (public) | Public docs, API reference, examples | Never |
| Your service account | Central service (your account) | Aggregated counts, Worker health, alerts, releases | Never |
| Administration | Your Worker | Licenses, customers, devices, sales | Yes, only in your account and only if you enable it |
Security rules for level 3
- Off by default. You turn it on in your Worker's settings and choose which tools it offers.
- Access through OAuth (or Cloudflare Access) with per-tool permissions: read-only by default.
- Tools that change something (revoke, extend, refund) ask for confirmation and are recorded in the admin change log as “via MCP”.
- Minimal answers: masked emails and no IP addresses by default; full data only when explicitly asked for and allowed.
- A clear warning: whatever the tools return reaches the provider of the assistant you use. That's your choice as the data controller.
- No new business logic: the same functions the admin already uses, exposed over remote MCP on HTTP in your own Worker.
In what order
Level 1 first, because it's cheap, touches no data and helps every maker integrate. Then level 3, which runs in your Worker. Level 2 only if the central service goes ahead.
Interested?
Join the waitlist and we'll let you know when the private beta opens. Nobody can use it or sign up for it yet.