Recurring Invoice Scheduler Subscription Billing Due Reminders MCP Server

by theluckystrike Your server? Claim it

answering

Recurring Invoice Scheduler Subscription Billing Due Reminders is answering right now. Last checked 13 min ago. It exposes 14 tools. Last commit 9 Sep 2026.

Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue.

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

218 ms

Response time

average over 24h

Stars

last commit 9 Sep 2026

What changed 21

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 September 2026. No other catalogue keeps this.

10 Sep 3 tool descriptions were rewritten license_activate, schedule_history, schedule_update

9 Sep 11 tool descriptions were rewritten17 times that day forecast, license_activate, license_status and 8 more

9 Sep a tool changed the parameters it asks for license_activate

and 6 more, back to 9 September 2026

What the code does

We read the source, 15 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Touches key and credential files data/npm_unblock.json:34

        "confound": "actions/setup-node with registry-url wrote NPM_CONFIG_USERCONFIG=$RUNNER_TEMP/.npmrc containing //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}; with no NODE_AUTH_TOKEN secret this expanded to the literal placeholder XXXXX-XXXXX-XXXXX-XXXXX, so npm authen…

Dumps the whole environment servers/office-suite/src/index.ts:126

  for (const [k, v] of Object.entries(process.env)) if (v !== undefined) env[k] = v;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add recurring-invoice-scheduler-subscription-billing-due-reminders --transport http https://mcp.zovo.one/mcp/recurring

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "recurring-invoice-scheduler-subscription-billing-due-reminders": {
      "url": "https://mcp.zovo.one/mcp/recurring"
    }
  }
}

~/.codex/config.toml

[mcp_servers.recurring-invoice-scheduler-subscription-billing-due-reminders]
url = "https://mcp.zovo.one/mcp/recurring"

.cursor/mcp.json

{
  "mcpServers": {
    "recurring-invoice-scheduler-subscription-billing-due-reminders": {
      "url": "https://mcp.zovo.one/mcp/recurring"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "recurring-invoice-scheduler-subscription-billing-due-reminders": {
      "url": "https://mcp.zovo.one/mcp/recurring"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

schedule

schedule_create

Define a repeating invoice: a client, the line items, how often to bill, and when it starts and ends. Returns the schedule id, a summary and its next dates. Nothing is invoiced until invoice_generate_due runs.

schedule_delete

Delete one schedule permanently. Invoices already generated stay in the invoice server and the history is kept. Re-creating it gives a NEW id, so its old periods count as unbilled. schedule_pause is reversible.

schedule_get

Return one schedule in full by id or client: items, cadence, dates, due days, anchor rules, notes, per-period amount, next due date and how many invoices it generated. schedule_history is the log.

schedule_history

The audit log for one schedule id, oldest first: period, invoice number, issue and due dates, amount, PDF path, and whether that invoice is unpaid, paid, skipped or since deleted. schedule_list finds the id. Pro.

schedule_list

List schedules: id, client, cadence, per-period amount and currency, start and end dates, status, next due date and auto_generate. Filter by status; a paused schedule reports no next due date.

schedule_pause

Stop one schedule generating invoices without deleting it; invoice_generate_due and forecast skip it. Its periods keep falling due and resuming back-bills them, so use schedule_skip to drop just one.

schedule_resume

Make a paused schedule active again. Every period missed while it was paused is still due and the next invoice_generate_due creates them all. Refused when it would pass the free tier's 3 active.

schedule_skip

Close ONE occurrence for good without pausing the schedule, reporting what will not be billed. period must be a real occurrence of it. An invoiced period is refused; undo reopens a skip.

schedule_upcoming

Table every occurrence of every ACTIVE schedule due in the next N days (30 default), with its amount and the invoice due date, plus a total per currency. Free lists the first 3 in your horizon.

schedule_update

Change one schedule by id: client, items, currency, cadence, dates, due_days, notes or auto_generate. Only the fields you pass change. Periods already invoiced are never re-issued, so a new amount applies to future ones.

license

license_activate

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

forecast

forecast

Expected invoiced revenue per calendar month per currency from active schedules. Invoiced and skipped periods are excluded and paused schedules listed apart. Free: 3 months; Pro: up to 120.

invoice

invoice_generate_due

Create a real invoice in the invoice server for every schedule occurrence on or before as_of that has not been invoiced yet, and render each PDF. Returns what was created, what was skipped and what is still due.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.zovo.one/mcp/recurring	streamable-http	answering	78 ms	13 min ago

Alternatives to Recurring Invoice Scheduler Subscription Billing Due Reminders

same job, measured the same way

Subscriptions

by theluckystrike

Recurring subscriptions billing: schedule once, auto-generate due invoice PDFs.

local only

Pdfapi MCP Server

by amranswill

Generate invoice, receipt, and report PDFs from structured JSON via a single API call.

20 installs/wk local only

Invoices Invoicing

by theluckystrike

Invoices and invoicing from your AI chat: PDF generation, numbering, VAT, overdue reports.

local only

Invovate MCP Server

by lightspeedplusone

AI-agent invoice generator: PDF, JSON & UBL in 11 languages via the Invovate API.

131 installs/wk local only

Factur-X e-invoicing

by leborgneantoine

Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1.

4 tools answering

Housecall Pro MCP

by hcpapi

Independent MCP server for the Housecall Pro API: jobs, estimates, invoices, price book, schedule.

56 installs/wk local only

Faktuj MCP

by dpozimski

Generate Polish VAT invoices (Faktura VAT) as PDF

31 installs/wk local only

Rendoc MCP Server

by yoryocoruxo-ai

Generate professional PDFs (invoices, contracts, reports) from AI tools via rendoc templates.

43 installs/wk local only

Recurring Invoice Scheduler Subscription Billing Due Reminders — questions

Answers built from our own checks of this server.

What can Recurring Invoice Scheduler Subscription Billing Due Reminders do?

It exposes 14 tools, read directly from the server on our last check. Among them: forecast, invoice_generate_due, license_activate, license_status, schedule_create, schedule_delete and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Recurring Invoice Scheduler Subscription Billing Due Reminders mostly used for?

Its tools cluster around schedule and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Recurring Invoice Scheduler Subscription Billing Due Reminders working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 218 ms. The bar chart above shows every period we have measured.

How do I connect Recurring Invoice Scheduler Subscription Billing Due Reminders?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Recurring Invoice Scheduler Subscription Billing Due Reminders need an API key?

No. Recurring Invoice Scheduler Subscription Billing Due Reminders completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Recurring Invoice Scheduler Subscription Billing Due Reminders?

It answers our handshake in 218 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Recurring Invoice Scheduler Subscription Billing Due Reminders open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.