SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Track billable hours: timers, timesheets, weekly totals, CSV export, unbilled hours to invoices.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 McpStamp Time Tracker。按照 https://mcp.popnx.com/i/theluckystrike-time-tracker-timesheet-billable-hours.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.zovo.one) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
McpStamp Time Trackerhttps://mcp.zovo.one/mcp/time-tracker在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsMcpStamp Time Tracker
用 McpStamp Time Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 McpStamp Time Tracker,或回答中出现 McpStamp Time Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
McpStamp Time Trackerhttps://mcp.zovo.one/mcp/time-tracker开启新聊天,输入前先从插件列表中选择 McpStamp Time Tracker
用 McpStamp Time Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 McpStamp Time Tracker,或回答中出现 McpStamp Time Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user time-tracker-timesheet-billable-hours https://mcp.zovo.one/mcp/time-tracker应能看到 McpStamp Time Tracker 在列表中并显示已连接
用 McpStamp Time Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 McpStamp Time Tracker,或回答中出现 McpStamp Time Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 McpStamp Time Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 McpStamp Time Tracker,或回答中出现 McpStamp Time Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 McpStamp Time Tracker 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 McpStamp Time Tracker,或回答中出现 McpStamp Time Tracker 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.zovo.one/mcp/time-trackerJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user time-tracker-timesheet-billable-hours https://mcp.zovo.one/mcp/time-trackerCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"time-tracker-timesheet-billable-hours": {
"url": "https://mcp.zovo.one/mcp/time-tracker"
}
}
}VS Code (mcp.json)
{
"servers": {
"time-tracker-timesheet-billable-hours": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/time-tracker"
}
}
}MCP_LICENSE_KEY 机密 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
license_statusReport 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_activateTurn 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.
timer_startStart a stopwatch for work on a project and return the start time. Only one runs at a time: a new one stops and logs the previous, naming it. rate is an hourly rate in MAJOR units for this timer only.
timer_stopStop the running timer and log it as one entry. Returns the duration, the money at the rate in force and the new entry id. With no timer running it says so and writes nothing.
timer_statusReport the running timer and today's total hours. Today is the local calendar day, so a timer started at 23:30 yesterday contributes only the minutes since midnight. No arguments, and it writes nothing.
entry_addLog time already worked as one entry and return its id, duration and amount. Give start plus end or minutes. rate is hourly in MAJOR units and is frozen on the entry, so a later rate change never moves it.
entry_logLog work time for a client/project in one step: minutes worked plus an optional note. The entry starts now minus the minutes, so it lands on today's day and week summaries.
summary_dayTotal hours logged for one calendar day (local date, default today), broken down per project.
summary_weekTotal hours logged in the week containing today (Mon-Sun, local dates), broken down per project.
summary_clientAll-time totals for one client/project: hours, entry count and billable amount, with a per-day breakdown.
target_setSet a weekly hours goal used by target_check. Stored locally.
target_checkCompare hours logged this week (Mon-Sun, local dates) against the weekly target from target_set.
entry_listList logged entries as a table of id, day, start, project, task, hours, billable, tags and note, newest first, with total hours. Free reads the last 7 days and says so; Pro reads the whole history.
entry_deleteDelete one logged entry by id and report the project and hours removed. It never touches a running timer. A billed entry goes too, losing the invoice record, so correct one with entry_edit instead.
entry_editChange one logged entry by id; only the fields you pass move. minutes keeps start and moves end, an end at or before start is refused, tags REPLACES the list, and rate is hourly in MAJOR units.
project_set_rateSet the hourly rate and currency used to turn tracked hours into money for a project or client. Returns the new rate and, when re-rating is asked for, how many already logged entries changed.
reportTimesheet report: total tracked hours and billable money for a period, optionally grouped by (group by) project, day, task or tag - hours per project, how much to bill. Omit group_by for the plain total per currency.
export_csvCall this tool to export the timesheet to a CSV file (excel-friendly) you can hand to a bookkeeper: one row per entry with hours, billable, rate, currency and amount. Returns the file path written.
entry_mark_billedClose the loop after an invoice is issued: stamp the tracked hours that went on it with the invoice number, so report and invoice_summary stop offering them and the same hours are never billed twice.
invoice_summaryTurn tracked billable time into invoice lines for one project: hours, hourly rate, amount per task and the total, one line per rate so two rates never average. Hours already marked billed are left out. Free: last 7 days.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 theluckystrike 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
在 614 毫秒内响应(HTTP 200)
无需登录
已读取 20 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/theluckystrike-time-tracker-timesheet-billable-hours)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于昨天,最新版本(0.23.0)于17天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
| 本项 McpStamp Time Tracker | SolidInvoice | Signal8 | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 是 | 否 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/6 | 5/5 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Featured on [Awesome MCP Servers](https://mcpservers.org) - directory listing | live hosted endpoint, free tier, no signup.
Track billable time without leaving your AI chat. Say "start a timer on the acme redesign", keep working, then ask for "my hours this week by project" or "invoice lines for acme in August". It keeps a running timer, lets you log time you forgot to track, applies your hourly rate per project, and turns the result into a report, a CSV file or a set of invoice line items. Everything is stored as plain JSON on your own machine.
Built by theluckystrike.
In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Ftime-tracker-timesheet-billable-hours/versions/latest) (io.github.theluckystrike/time-tracker-timesheet-billable-hours).
Listed on the [AI Product Index](https://index.percall.dev/l/zovo-time-tracker.html) - live remote endpoint at mcp.zovo.one/s/time-tracker, free tier, no signup.
Track billable time from chat and turn it straight into a report or invoice line items, zero setup, all local.
npm publish for @theluckystrike/mcp-time-tracker 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 time-tracker.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": { "time-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-time-tracker"] } } }
Claude Code:
claude mcp add time-tracker -- npx -y @theluckystrike/mcp-time-tracker
(.cursor/mcp.json):
{
"mcpServers": { "time-tracker": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-time-tracker"] } } }
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/time-tracker
Then point your client's command at node with one arg: the absolute path to servers/time-tracker/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.
| Tool | What it does |
|---|---|
timer_start | Start a timer on a project (optional task, tags, rate, currency). Starting a new one stops and logs the old one. A partial project name that matches exactly one existing project is used as that project. |
timer_stop | Stop the running timer, write the entry, return the duration. |
timer_status | What is running, for how long, and today's total. |
entry_add | Log time you already worked (start plus end or minutes), with an optional rate and currency: rate "90 euros an hour" bills as EUR 225.00 for 2.5 h. Partial project names resolve like timer_start. |
entry_list | Compact table of entries, filtered by date range and project. |
entry_edit | Change any field of an entry. |
entry_delete | Delete an entry by id. |
project_set_rate | Set the hourly rate and currency used for money totals (currency accepts codes or words: EUR, euros, pounds, zl). apply_to_existing: true re-rates time already logged for that project; add only_missing: true to touch only entries that carry no rate. |
report | Hours and money for a period, optionally grouped by project, day, task or tag; omit group_by for the plain total per currency. Table, JSON or CSV. Hours already invoiced are left out; pass unbilled_only: false for the full timesheet. |
export_csv | Write entries to a CSV file and return the path. |
invoice_summary | Invoice-ready line items for one project: hours, rate, amount, total, in the currency the time was logged in. One line per task and rate, so no line ever shows a blended rate nobody agreed. Returns the entry_ids behind the lines, and skips hours already invoiced (unbilled_only: false includes them). Free for the last 7 days, Pro for any period from full history. |
entry_mark_billed | Stamp the hours that went on an invoice with its number (ids from invoice_summary, or project + from + to), so report and invoice_summary stop offering them and the same hours are never billed twice. |
license_status | Free or Pro, and where to upgrade. |
license_activate | Activate a Pro key (verified offline). |
Also exposed: the resource timetracker://today (today's summary) and the prompt daily_standup (writes a standup update from yesterday's and today's tracked time).
No tool names required. These are the sentences that were actually tested against the server; the tool column is what answered them.
| You say | Tool |
|---|---|
| "Start a timer for the Acme website project." | timer_start |
| "Stop the timer and tell me how long I worked." | timer_stop |
| "What's running right now, and for how long?" | timer_status |
| "Log 2.5 hours yesterday for Acme, design review, at 90 euros an hour." | entry_add |
| "Show me my Acme entries for this week." | entry_list |
| "That last entry should say API refactor, not design review." | entry_edit |
| "Delete the entry I just logged twice." | entry_delete |
| "Set my rate for Acme to 90 EUR an hour." | project_set_rate |
| "How many hours did I bill this month, grouped by project?" | report |
| "Give me invoice lines for Acme in August." | invoice_summary |
| "I invoiced those hours as INV-2026-0001." | entry_mark_billed |
Two more worth knowing: "export my time to a CSV for my bookkeeper" (export_csv) and "write my standup update from yesterday and today" (the daily_standup prompt).
This is a real transcript from the audit in docs/USER_VALUE_R2.md, numbers unchanged.
You: Log 2.5 hours yesterday for Acme, design review, at 90 euros an hour.
entry_add { project: "Acme", ... } -> "Acme" resolved to the existing project "Acme website" -> rate "90 euros an hour" parsed as EUR 90.00/h
Assistant: Logged 2.50 h for Acme website - design review at EUR 90.00/h = EUR 225.00.
You: How much do I bill Acme this week? Give me invoice lines.
invoice_summary { project: "Acme website", from: "2026-08-31", to: "2026-09-02" }
Assistant: Invoice summary - Acme website design review 2.50 h EUR 90.00/h EUR 225.00 TOTAL 2.50 h EUR 225.00
One call each. The rate carries its currency all the way through: the report never prints a bare "225", and it never turns into "$225" by accident.
A second worked example, the weekly report and the daily_standup prompt:
You: How many hours did I put into Acme this week, grouped by task?
report { project: "Acme website", from: "2026-08-27", to: "2026-09-02", group_by: "task" }
Assistant: Acme website, 2026-08-27 to 2026-09-02 design review 2.50 h EUR 225.00 TOTAL 2.50 h EUR 225.00
You: Write my standup update.
(prompt) daily_standup
Assistant: Yesterday: 2.50 h on Acme website (design review). Today: nothing logged yet.
An hour that has been invoiced is finished. entry_mark_billed {ids, invoice_number} writes billed_at and billed_invoice onto those entries; from then on report and invoice_summary skip them by default, so next month's "invoice Acme" cannot re-bill work already paid for. The whole timesheet is still there: pass unbilled_only: false to any of them. invoice_summary returns the entry_ids it used precisely so they can be handed straight to entry_mark_billed once the invoice exists.
report and invoice_summary answer overlapping questions on purpose: report is for "how much time and money," grouped any way you like; invoice_summary is for "give me the lines I can put on an invoice," which is a narrower, invoice-shaped view of the same entries for one project.
Entries, projects and rates live in one JSON file: ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/time-tracker/data.json.
Every write (starting or stopping a timer, adding, editing or deleting an entry, setting a rate) happens under an advisory lock file at .../time-tracker/.lock, held across the whole load-mutate-save cycle, so two overlapping calls cannot interleave and corrupt the file. The save itself writes to a temporary file and renames it into place, so a crash or a killed process mid-write leaves either the old file or the new one, never a half-written one. Reads (entry_list, report, timer_status, export_csv) do not take the lock.
To back up your data, copy the single data.json file (and .lock if present, though it holds no data). There is no database and no hidden second file.
If data.json is ever unreadable or not valid JSON, the server does not treat that as "no data yet". It moves the file aside byte-for-byte as data.json.corrupt- , writes a data.json.corrupt marker and makes every tool, reads included, return data file is corrupt; moved to ...; nothing was written. Restore a good data.json (the quarantined copy is right there) and delete the marker file to carry on. Nothing is overwritten in the meantime.
2026-09-02T09:00:00 means 09:00 where you are, not UTC. Pass an explicit offset (2026-09-02T09:00:00+02:00) or a trailing Z and it is honoured exactly.from: "2026-09-01" is 00:00:00 local on the 1st and to: "2026-09-30" is 23:59:59.999 local on the 30th, so a month reported by dates includes its last day. Timestamps with a time are used as given.from or ends after to counts for the part inside the period, not all of it and not none of it.timer_status counts only the part of an entry, or of the running timer, that falls after midnight today."1,200 USD" is 1200 (a comma followed by exactly three digits is thousands grouping), "12,50 EUR" is 12.50 (the unambiguous European decimal shape), and "1.200,50" is 1200.50. Anything that could mean either thing, such as "1,2345", is refused with a worked example instead of being read as the wrong number.entry_add and timer_stop store the effective hourly rate and currency on the entry, and reports and invoices use that stored rate. project_set_rate therefore applies to future entries only; pass apply_to_existing: true to re-rate the time already logged for that project. That re-stamps EVERY entry of the project, including entries that already carry a rate, and the response says how many changed and the project's new total. Add only_missing: true to touch only entries that captured no rate of their own.group_by: "tag" an entry tagged dev and meeting appears in both rows; the total is computed from the entries once, so it is never the sum of the rows.entry_list, report, export_csv and invoice_summary only see the last 7 days. T