Vibecode Tallymeter
track this build5 steps, step by step0%KINDA · weekend project
price $10.38/moyou'd save $124.56/yrbuild time weekendcategory 🧾 finance & accountingreplaced by 0 people
The solo core is a weekend build and nobody should pretend otherwise: a timer, projects with hourly rates, and uninvoiced hours rolled into a numbered PDF. What survives the rebuild is the boring half · two-way Jira worklog sync that reconciles ticket by ticket without double-counting, a hosted MCP server and scoped API tokens your agents can reach from any machine, and invoice numbering plus VAT and bank details that hold up when an accountant reads them. Full disclosure: this entry was submitted by the person who builds Tallymeter. Same rubric as everything else on the list, and the honest answer is that a freelancer billing one client can absolutely one-shot the part they use.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Tallymeter. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Tallymeter indie build ## Goal Build the smallest trustworthy replacement for the core Tallymeter workflow for one developer or a tiny team. ## Scope Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - two-way Jira Cloud worklog sync that reconciles ticket by ticket - a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution - invoice numbering, VAT and bank details that survive an accountant handoff - shared team workspaces and per-member unbilled totals - managed hosting, nightly backups and a phone-sized UI for starting a timer away from your desk If those capabilities are essential, use kimai instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a freelance time tracker that produces invoices, like Tallymeter. Requirements: - Node + Express + better-sqlite3, one process, server-rendered pages on localhost:4820. No accounts, no telemetry, everything stays on my machine. - Tables: clients, projects (hourly rate, currency), entries, invoices. - One timer, big start/stop button on the index page: starting a new one stops the running one first, so two can never run at once. Entries store description, project, started_at and ended_at as ISO-8601 UTC. - Let me edit a finished entry's description in place, and add one after the fact with a duration in minutes for the call I forgot to track. Entries already on an invoice are frozen, reject the edit. - An /unbilled page: finished entries with no invoice_id, grouped by project, hours shown as "3h 25m" and the money at the project rate. - Invoice a project's unbilled entries: one line per description with decimal hours, sequential INV-2026-001 numbers that are never reused even if I delete a draft, bank details and VAT rate from config.json, rendered to ./invoices/INV-2026-001.pdf with puppeteer. Stamp invoice_id on what it billed. - Out of scope: multi-user accounts, payment collection, mobile apps. Skip them. - README: config.json fields, where the PDFs land, and a warning that the sqlite file is the only copy of my billing history · tell me to back it up. ## Required capabilities - an always-on box if you want the timer off your laptop - PDF generation - Jira API credentials if you want worklog sync - backups you actually test ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Tallymeter. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Tallymeter indie build ## Goal Build the smallest trustworthy replacement for the core Tallymeter workflow for one developer or a tiny team. ## Scope Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - two-way Jira Cloud worklog sync that reconciles ticket by ticket - a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution - invoice numbering, VAT and bank details that survive an accountant handoff - shared team workspaces and per-member unbilled totals - managed hosting, nightly backups and a phone-sized UI for starting a timer away from your desk If those capabilities are essential, use kimai instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a freelance time tracker that produces invoices, like Tallymeter. Requirements: - Node + Express + better-sqlite3, one process, server-rendered pages on localhost:4820. No accounts, no telemetry, everything stays on my machine. - Tables: clients, projects (hourly rate, currency), entries, invoices. - One timer, big start/stop button on the index page: starting a new one stops the running one first, so two can never run at once. Entries store description, project, started_at and ended_at as ISO-8601 UTC. - Let me edit a finished entry's description in place, and add one after the fact with a duration in minutes for the call I forgot to track. Entries already on an invoice are frozen, reject the edit. - An /unbilled page: finished entries with no invoice_id, grouped by project, hours shown as "3h 25m" and the money at the project rate. - Invoice a project's unbilled entries: one line per description with decimal hours, sequential INV-2026-001 numbers that are never reused even if I delete a draft, bank details and VAT rate from config.json, rendered to ./invoices/INV-2026-001.pdf with puppeteer. Stamp invoice_id on what it billed. - Out of scope: multi-user accounts, payment collection, mobile apps. Skip them. - README: config.json fields, where the PDFs land, and a warning that the sqlite file is the only copy of my billing history · tell me to back it up. ## Required capabilities - an always-on box if you want the timer off your laptop - PDF generation - Jira API credentials if you want worklog sync - backups you actually test ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Tallymeter. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Tallymeter product brief ## Problem The solo core is a weekend build and nobody should pretend otherwise: a timer, projects with hourly rates, and uninvoiced hours rolled into a numbered PDF. What survives the rebuild is the boring half · two-way Jira worklog sync that reconciles ticket by ticket without double-counting, a hosted MCP server and scoped API tokens your agents can reach from any machine, and invoice numbering plus VAT and bank details that hold up when an accountant reads them. Full disclosure: this entry was submitted by the person who builds Tallymeter. Same rubric as everything else on the list, and the honest answer is that a freelancer billing one client can absolutely one-shot the part they use. ## Product outcome Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - an always-on box if you want the timer off your laptop - PDF generation - Jira API credentials if you want worklog sync - backups you actually test ## Explicit non-goals for v1 - two-way Jira Cloud worklog sync that reconciles ticket by ticket - a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution - invoice numbering, VAT and bank details that survive an accountant handoff - shared team workspaces and per-member unbilled totals - managed hosting, nightly backups and a phone-sized UI for starting a timer away from your desk ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a freelance time tracker that produces invoices, like Tallymeter. Requirements: - Node + Express + better-sqlite3, one process, server-rendered pages on localhost:4820. No accounts, no telemetry, everything stays on my machine. - Tables: clients, projects (hourly rate, currency), entries, invoices. - One timer, big start/stop button on the index page: starting a new one stops the running one first, so two can never run at once. Entries store description, project, started_at and ended_at as ISO-8601 UTC. - Let me edit a finished entry's description in place, and add one after the fact with a duration in minutes for the call I forgot to track. Entries already on an invoice are frozen, reject the edit. - An /unbilled page: finished entries with no invoice_id, grouped by project, hours shown as "3h 25m" and the money at the project rate. - Invoice a project's unbilled entries: one line per description with decimal hours, sequential INV-2026-001 numbers that are never reused even if I delete a draft, bank details and VAT rate from config.json, rendered to ./invoices/INV-2026-001.pdf with puppeteer. Stamp invoice_id on what it billed. - Out of scope: multi-user accounts, payment collection, mobile apps. Skip them. - README: config.json fields, where the PDFs land, and a warning that the sqlite file is the only copy of my billing history · tell me to back it up. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Tallymeter capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Tallymeter indie build ## Goal Build the smallest trustworthy replacement for the core Tallymeter workflow for one developer or a tiny team. ## Scope Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - two-way Jira Cloud worklog sync that reconciles ticket by ticket - a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution - invoice numbering, VAT and bank details that survive an accountant handoff - shared team workspaces and per-member unbilled totals - managed hosting, nightly backups and a phone-sized UI for starting a timer away from your desk If those capabilities are essential, use kimai instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a freelance time tracker that produces invoices, like Tallymeter. Requirements: - Node + Express + better-sqlite3, one process, server-rendered pages on localhost:4820. No accounts, no telemetry, everything stays on my machine. - Tables: clients, projects (hourly rate, currency), entries, invoices. - One timer, big start/stop button on the index page: starting a new one stops the running one first, so two can never run at once. Entries store description, project, started_at and ended_at as ISO-8601 UTC. - Let me edit a finished entry's description in place, and add one after the fact with a duration in minutes for the call I forgot to track. Entries already on an invoice are frozen, reject the edit. - An /unbilled page: finished entries with no invoice_id, grouped by project, hours shown as "3h 25m" and the money at the project rate. - Invoice a project's unbilled entries: one line per description with decimal hours, sequential INV-2026-001 numbers that are never reused even if I delete a draft, bank details and VAT rate from config.json, rendered to ./invoices/INV-2026-001.pdf with puppeteer. Stamp invoice_id on what it billed. - Out of scope: multi-user accounts, payment collection, mobile apps. Skip them. - README: config.json fields, where the PDFs land, and a warning that the sqlite file is the only copy of my billing history · tell me to back it up. ## Required capabilities - an always-on box if you want the timer off your laptop - PDF generation - Jira API credentials if you want worklog sync - backups you actually test ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Tallymeter product brief ## Problem The solo core is a weekend build and nobody should pretend otherwise: a timer, projects with hourly rates, and uninvoiced hours rolled into a numbered PDF. What survives the rebuild is the boring half · two-way Jira worklog sync that reconciles ticket by ticket without double-counting, a hosted MCP server and scoped API tokens your agents can reach from any machine, and invoice numbering plus VAT and bank details that hold up when an accountant reads them. Full disclosure: this entry was submitted by the person who builds Tallymeter. Same rubric as everything else on the list, and the honest answer is that a freelancer billing one client can absolutely one-shot the part they use. ## Product outcome Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - an always-on box if you want the timer off your laptop - PDF generation - Jira API credentials if you want worklog sync - backups you actually test ## Explicit non-goals for v1 - two-way Jira Cloud worklog sync that reconciles ticket by ticket - a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution - invoice numbering, VAT and bank details that survive an accountant handoff - shared team workspaces and per-member unbilled totals - managed hosting, nightly backups and a phone-sized UI for starting a timer away from your desk ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a freelance time tracker that produces invoices, like Tallymeter. Requirements: - Node + Express + better-sqlite3, one process, server-rendered pages on localhost:4820. No accounts, no telemetry, everything stays on my machine. - Tables: clients, projects (hourly rate, currency), entries, invoices. - One timer, big start/stop button on the index page: starting a new one stops the running one first, so two can never run at once. Entries store description, project, started_at and ended_at as ISO-8601 UTC. - Let me edit a finished entry's description in place, and add one after the fact with a duration in minutes for the call I forgot to track. Entries already on an invoice are frozen, reject the edit. - An /unbilled page: finished entries with no invoice_id, grouped by project, hours shown as "3h 25m" and the money at the project rate. - Invoice a project's unbilled entries: one line per description with decimal hours, sequential INV-2026-001 numbers that are never reused even if I delete a draft, bank details and VAT rate from config.json, rendered to ./invoices/INV-2026-001.pdf with puppeteer. Stamp invoice_id on what it billed. - Out of scope: multi-user accounts, payment collection, mobile apps. Skip them. - README: config.json fields, where the PDFs land, and a warning that the sqlite file is the only copy of my billing history · tell me to back it up. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Tallymeter capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
The timer is a weekend. The failure modes are not. Uninvoiced time that silently double-counts against a Jira worklog, an invoice sequence with a gap in it, or a laptop that was asleep when the agent tried to log its hours are all problems you discover on invoice day, in front of a client. A business billing real money for hours generally decides that maintaining the thing that produces its invoices is not the hobby it wants.
xtwo-way Jira Cloud worklog sync that reconciles ticket by ticket
xa hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution
xinvoice numbering, VAT and bank details that survive an accountant handoff
xshared team workspaces and per-member unbilled totals
xmanaged hosting, nightly backups and a phone-sized UI for starting a timer away from your desk
share on X ↗"I just replaced Tallymeter ($10.38/mo) with one prompt"
Don't feel like building it? These folks already made it free.
KimaiTime, expenses, numbered invoices and a JSON API; the MCP server is the missing party trick.open source↗
Invoice Ninja self-hostedTime entries become numbered invoices and the API is usable; agents do not get a ready-made MCP server.free↗no votes, no pay-to-list · just what's real
Tallymeter pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| pro | $10.38/workspace | $8.65/workspace | Unlimited projects and clients; reports, CSV exports, numbered invoices, Jira integration, REST API, and MCP server |
free tierno free tier; 30-day trial with no card
billingmonthly + annual (annual is 2 months free)
verified 2026-08-10 · source ↗
Vibecode Tallymeter
Kinda. The core of Tallymeter is buildable in a weekend with the prompt on this page, but there are real gaps: two-way Jira Cloud worklog sync that reconciles ticket by ticket, a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution. Read the honest list above before committing.
How much does Tallymeter cost?
Tallymeter costs about $10.38/month (Pro, checked 2026-08-10), which is $124.56 per year.
What do I lose by replacing Tallymeter?
Honestly: two-way Jira Cloud worklog sync that reconciles ticket by ticket; a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution; invoice numbering, VAT and bank details that survive an accountant handoff; shared team workspaces and per-member unbilled totals; managed hosting, nightly backups and a phone-sized UI for starting a timer away from your desk. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Tallymeter?
Yes: Kimai (Time, expenses, numbered invoices and a JSON API; the MCP server is the missing party trick.) Invoice Ninja self-hosted (Time entries become numbered invoices and the API is usable; agents do not get a ready-made MCP server.) The prompt is for when you want it exactly your way.