Subscription management MCP with scoped read and write tools
The LemSubs MCP is not a read-only dashboard wrapper. With explicit write scopes, an assistant can add or update subscription records, record a price change, set a renewal reminder and archive an entry through reversible, audited actions.
At a glance
| Question | Answer |
|---|---|
| Default access | Read-only scopes |
| Writes | Separate stack, note, tag and spend scopes |
| Destructive action | Archive requires an in-client confirmation token |
| Retry safety | Write calls support a 24-hour idempotency key |
| Auditability | Tool, client, result and time are logged |
Real subscription-management actions
The write catalog covers the work an assistant can perform safely against a subscription register. It does not log in to a vendor account, move money or change a third-party billing agreement.
- Add a subscription or create one from invoice details.
- Update name, category, cycle, renewal date or vendor URL.
- Record a price change or change the tracked status.
- Set a renewal reminder, add a note, add tags or attach a public receipt URL.
- Archive a record after explicit confirmation; restore it later from the LemSubs UI.
Permissions stay narrow
Reading the stack, costs, renewals, lifetime deals, licences and recommendations are separate scopes. Writes are split again so an assistant that only adds notes does not need permission to archive a record or change spend data.
OAuth tokens are audience-bound to the LemSubs MCP resource. Bearer keys are stored hashed, can be restricted to workspaces, and should be created one per client.
Questions people ask
Can an assistant add a subscription from an invoice?
Yes. Supply the vendor, amount, currency, billing cycle and optional renewal date. A public invoice URL can be attached to the new record; private files are not fetched by the MCP server.
Can it update or archive a subscription?
Yes, when the connection has stack:write. Archiving requires a short-lived confirmation token and remains reversible in the LemSubs UI for 30 days.
Are repeated write calls safe?
Clients can send an Idempotency-Key header. LemSubs deduplicates the same write for 24 hours and returns the original result.