原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Subscription Manager Track Renewals

作者:theluckystrike版本 0.23.1i★ 2 (整个仓库的星标)i在云端运行官方网站 ↗
注册名称io.github.theluckystrike/subscription-manager-track-renewals

安装方法

What it does

Track subscriptions and renewals from your AI chat: schedules, due dates, reminders, local data.

  • Connects 在云端运行
  • Account or key Needs Authorization
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Subscription Manager Track Renewals。按照 https://mcp.popnx.com/i/theluckystrike-subscription-manager-track-renewals.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.zovo.one) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 Subscription Manager Track Renewals 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Subscription Manager Track Renewals 网站 ↗

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Subscription Manager Track Renewals
    Remote MCP server URL · 地址https://mcp.zovo.one/mcp/subscription-manager-track-renewals

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +ConnectorsSubscription Manager Track Renewals

  5. 试一试

    用 Subscription Manager Track Renewals 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Subscription Manager Track Renewals,或回答中出现 Subscription Manager Track Renewals 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Subscription Manager Track Renewals

Subscription Manager Track Renewals 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 Subscription Manager Track Renewals 的应用

  • 需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建)
  • 需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建)
  • 需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建)

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建)

  1. 注册并创建 Subscription Manager Track Renewals 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Subscription Manager Track Renewals 网站 ↗

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user subscription-manager-track-renewals https://mcp.zovo.one/mcp/subscription-manager-track-renewals --header 'Authorization: Bearer your-value'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 Subscription Manager Track Renewals 在列表中并显示已连接

  5. 试一试

    用 Subscription Manager Track Renewals 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Subscription Manager Track Renewals,或回答中出现 Subscription Manager Track Renewals 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建)

  1. 注册并创建 Subscription Manager Track Renewals 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Subscription Manager Track Renewals 网站 ↗

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Subscription Manager Track Renewals 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Subscription Manager Track Renewals 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Subscription Manager Track Renewals,或回答中出现 Subscription Manager Track Renewals 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 Subscription Manager Track Renewals 的密钥(在开发者网站创建)

  1. 注册并创建 Subscription Manager Track Renewals 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Subscription Manager Track Renewals 网站 ↗

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Subscription Manager Track Renewals 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Subscription Manager Track Renewals 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Subscription Manager Track Renewals,或回答中出现 Subscription Manager Track Renewals 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.zovo.one/mcp/subscription-manager-track-renewals

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Subscription Manager Track Renewals 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user subscription-manager-track-renewals https://mcp.zovo.one/mcp/subscription-manager-track-renewals --header 'Authorization: Bearer your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "subscription-manager-track-renewals": {
      "url": "https://mcp.zovo.one/mcp/subscription-manager-track-renewals",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "subscription-manager-track-renewals": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/subscription-manager-track-renewals",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Bearer

说明仍为英文原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

GitHub 星标i
2 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
不在 npm/PyPI 上
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.23.1
分类i
其他
发布到注册中心i
2026年9月24日
代码最后更新i
2026年11月18日
最近检查
2026年11月14日
作者
theluckystrike
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • 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_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_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_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.

  • 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_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_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.

  • 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.

  • 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.

  • 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.

  • 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.

  • license_activate

    Turn Pro on for this connection with key, an MCPL1. . 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.

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 theluckystrike 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 MIT

  • ✓ 通过

    端点有响应

    在 578 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 14 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/theluckystrike-subscription-manager-track-renewals.svg)](https://mcp.popnx.com/en/servers/theluckystrike-subscription-manager-track-renewals)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20653 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20653 个服务器的 44% 更新
  • 基础检查结果等于或优于此分类中其他 20653 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Subscription Manager Track Renewals 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.23.1)于2个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582514个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
Subscription Manager Track Renewals
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/54/44/44/41/44/4
许可证MITAGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mcp-recurring

Say "bill Acme 12 hours at 90 EUR on the 1st of every month" once, and stop remembering it. This MCP server stores recurring invoice schedules, client, line items, cadence, start and end dates, and then, when you ask, creates the invoices that have actually fallen due as real records in the invoice server, with its number series, its clients and its A4 PDF. Generation is idempotent: one invoice per schedule per period, keyed by the occurrence date, so running the billing run twice on the same day creates nothing the second time. It also answers "what falls due in the next 30 days" and "what will I invoice per month for the next year". Everything is stored in plain JSON files on your own machine; nothing is uploaded anywhere.

In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Frecurring-invoice-scheduler-subscription-billing-due-reminders/versions/latest) (io.github.theluckystrike/recurring-invoice-scheduler-subscription-billing-due-reminders).

Define a repeating invoice once, generate the due PDFs from chat, no billing SaaS required.

60-second install

npm publish for @theluckystrike/mcp-recurring is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.

One-click (.mcpb): download recurring.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

(claude_desktop_config.json):

{

"mcpServers": { "recurring": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-recurring"] } } }

Claude Code:

claude mcp add recurring -- npx -y @theluckystrike/mcp-recurring

(.cursor/mcp.json):

{

"mcpServers": { "recurring": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-recurring"] } } }

The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these three commands:

git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers

npm install npm run build -w packages/mcp-license -w servers/invoice -w servers/recurring

Then point your client's command at node with one arg: the absolute path to servers/recurring/dist/index.js.

To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.

Pairs with

  • [mcp-invoice](../invoice), required in practice, not by code. This server writes into the invoice server's data directory and shares its number counter, its client list and its business profile, so every generated invoice appears in invoice_list, counts in overdue_report and can be re-rendered with invoice_pdf. Set your issuer details once with business_set there; this server has no business_set of its own on purpose, so there is only one profile to keep right.
  • [mcp-time-tracker](../time-tracker), for the hours that are not on a retainer. Track them, invoice them ad hoc, and leave the fixed monthly part to a schedule here.
  • [mcp-expense-tracker](../expense-tracker), rebillable costs that change every month belong on an ad hoc invoice; a schedule is for the amount that does not change.

Tools

ToolWhat it does
schedule_createDefine a repeating invoice: client, items, cadence, start date, optional end date, due days, notes
schedule_listEvery schedule with cadence, amount per period, next due date and status
schedule_getFull record for one schedule, plus how many invoices it has generated
schedule_updateChange client, items, currency, cadence, dates, due days or notes. Periods already invoiced are never re-issued
schedule_pauseStop generating without deleting; history is kept
schedule_resumeMake it active again. Periods that fell due while paused are still due
schedule_deleteRemove the schedule. Invoices it made stay in the invoice server and its history is kept as an audit trail. A re-created schedule gets a new id, so invoice_generate_due warns when it re-covers a period the old one already billed
schedule_skipSkip ONE occurrence for good, without pausing the schedule -- the answer to "do not bill this client for October". undo: true puts the period back
schedule_upcomingWhat falls due in the next N days, with amounts and totals per currency, plus any period that already fell due and was never invoiced. Free covers 30 days
invoice_generate_dueCreate the invoices that are due as of a date and render their PDFs. Idempotent, keyed by period; reports created and skipped. At most 60 invoices per call, oldest period first, and it says how many are still due. dry_run shows the run first. Free and unlimited
schedule_historyPro: the audit log for one schedule -- every period, invoice number, dates, amount, paid status and PDF path
forecastExpected revenue per calendar month per currency, with paused schedules listed separately rather than dropped. Free covers 3 months
license_statusShow free or Pro mode
license_activateActivate a Pro key (verified offline)

Resource: recurring://upcoming returns the next 30 days of occurrences as JSON. Prompt: monthly_billing_run, dry run, generate, list what is coming, then report who needs a payment reminder.

What you can say

You sayTool
"Bill Acme 12 hours at 90 EUR every month from the 1st."schedule_create
"What recurring invoices do I have?"schedule_list
"What is due in the next 30 days?"schedule_upcoming
"Run this month's billing."monthly_billing_run / invoice_generate_due
"Show me what would be created before you create it."invoice_generate_due {dry_run: true}
"Pause the Beta Corp retainer, they are on hold."schedule_pause
"Do not bill Acme for October."schedule_skip
"Put the Acme retainer up to 100 EUR an hour from now on."schedule_update
"How much will I invoice per month next year?"forecast
"Show me every invoice this retainer has produced."schedule_history

Worked example

You: Bill Acme 12 hours at 90 EUR a month, starting 1 June, 14 day terms.

schedule_create { client: "Acme Retainer", currency: "EUR", every: "monthly", start_date: "2026-06-01", due_days: 14, items: [{ description: "Retainer hours", quantity: 12, unit_price: 90 }] } -> schedule 9f2c1a04, next dates 2026-06-01, 2026-07-01, 2026-08-01, 2026-09-01

You (on 3 September): Run the billing.

invoice_generate_due {} -> as_of 2026-09-03: created 4 invoices, skipped 0 already invoiced. INV-2026-0001 Acme Retainer period 2026-06-01 EUR 1080.00 due 2026-06-15 .../pdf/INV-2026-0001.pdf INV-2026-0002 Acme Retainer period 2026-07-01 EUR 1080.00 due 2026-07-15 .../pdf/INV-2026-0002.pdf INV-2026-0003 Acme Retainer period 2026-08-01 EUR 1080.00 due 2026-08-15 .../pdf/INV-2026-0003.pdf INV-2026-0004 Acme Retainer period 2026-09-01 EUR 1080.00 due 2026-09-15 .../pdf/INV-2026-0004.pdf Total: EUR 4320.00

You (five minutes later, having forgotten): Run the billing.

invoice_generate_due {} -> as_of 2026-09-03: created 0 invoices, skipped 4 already invoiced.

The second run is the point: the period, not the calendar day, is the key, so a repeated billing run is a no-op rather than a duplicate invoice sitting in a client's inbox.

Free vs Pro

FreePro
Active schedules3Unlimited
invoice_generate_dueYes, unlimitedYes, unlimited
schedule_upcoming horizon30 daysUp to 10 years
forecast3 monthsUp to 120 months
schedule_history audit logNoYes
End-of-month and anchor-day rules (anchor_day, end_of_month)No, bills on the start date's day of monthYes
Pause, resume, update, delete, dry run, multi-currencyYesYes

Pro is a one-time $19, or $39 for every server in the collection, lifetime.

Dates: what happens at a month end

Every date is a local ISO calendar date, YYYY-MM-DD. An occurrence is the k-th step from start_date, and occurrence 0 is start_date itself, so a schedule starting today is due today.

  • weekly = +7 days per step. {days: n} = +n days per step.
  • monthly = +1 month, quarterly = +3 months, yearly = +12 months.
  • Month ends. The month step keeps the day of month of start_date and clamps it to the length of the target month; it never carries the clamp forward. From 2026-01-31 the series is 01-31, 02-28, 03-31, 04-30, 05-31, February does not silently turn a month-end retainer into a 28th-of-the-month retainer.
  • Feb 29. The same rule makes a yearly schedule starting 2028-02-29 fall on 02-28 in common years and back on 02-29 in the next leap year.
  • `anchor_day` / `end_of_month` (Pro). anchor_day replaces the day of month before clamping, so anchor_day: 31 means the last day of every month; end_of_month: true does the same explicitly. Both are ignored for weekly and {days: n}, which have no month to anchor to. An anchored first occurrence that would land before start_date is dropped, never billed early.
  • `end_date` is inclusive. An occurrence landing exactly on end_date is generated; the next one is not.
  • Long-lived schedules. Looking up what is due does not replay the schedule from start_date: it jumps to an estimate near the date you asked about and scans forward from there, so a daily schedule created in 2010 still reports what is due in 2026 instead of exhausting its per-run occurrence cap walking there one day at a time.

Money

Amounts are held as integer minor units by the invoice engine, the same ISO 4217 table, the same round-per-line-then-sum contract, so a schedule's amount and the invoice it produces can never disagree. Each line's gross is rounded first, tax is computed and rounded per line and grouped into one line per rate, and the totals are integer sums of those already-rounded values. A schedule bills in its own currency, or your business default currency if it has none; nothing here converts between currencies.

How it stores data

Schedules and the generation log live in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/recurring/ as schedules.json and history.json. The go into the invoice server's directory, ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/invoice/, with their PDFs under its pdf/ subfolder, the same files invoice_list, overdue_report and invoice_pdf read there.

Every mutation runs under an advisory lock file. Anything that writes an invoice takes two locks, always in the same order, recurring/.lock first, then invoice/.lock, so two billing runs (or a billing run and a hand-written invoice in the other server) cannot interleave, cannot allocate the same invoice number and cannot deadlock. Invoice numbers are allocated inside the lock; the PDFs are rendered after it is released, so a slow render never holds up the counter. Saves go to a temporary file and are renamed into place.

If schedules.json or history.json is unreadable or not valid JSON it is never treated as "empty": the file is moved aside byte-for-byte as .json.corrupt- , a .json.corrupt marker is written, and every tool fails loudly until you restore a good copy and delete the marker. This matters more here than anywhere else in the collection: a history.json silently read as empty would re-bill every period the schedule has ever covered.

Limits and honest caveats

  • Nothing runs in the background. This is a stdio MCP server: it exists while your client runs it. No daemon, no cron, no email. Invoic

只显示了开头部分;其余内容请在仓库中阅读