Invoice

io.github.LAHutchins91v1.0.1Updated Oct 5, 2026

Approved freelance invoice: line items, rates, due date, and late terms, over MCP.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant read a freelancer's approved invoice record and propose changes that only take effect after explicit approval.

What it does
Invoice stores one freelancer's approved invoice — line items, quantities, approved rates, due date, and late terms — and exposes tools to list, begin, and read invoices, place and describe lines, set quantities and due dates, write late terms, offer discounts, and seal an invoice. Once sealed, direct edits such as new lines, changed rates, discounts, or moved due dates are refused; changes must go through suggest_invoice_change and then accept_invoice_change with explicit approval. read_invoice is the read the assistant should perform before answering.
When to use it
Useful when an assistant needs to answer questions about a specific approved freelance invoice, or to draft and propose invoice changes while keeping the approved record authoritative. It is not a general accounting or billing system.
Requirements
Remote endpoint at the provider's URL, or a self-hosted instance (Node.js; npm install, build, start) with the base URL you configure; the default local MCP address is OAuth sign-in with an Invoice account is required; tools need Pro or an active trial. Server-side environment variables include APP_BASE_URL, SUPABASE_URL, SUPABASE_ANON_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRICE_MONTHLY, STRIPE_PRICE_YEARLY, and INVOICE_DATA_PATH. No API key or password should be placed in a…
Before you install
Tool calls require a signed-in account with an active or trialing subscription, and a new subscription includes a 14-day trial; checkout shows billing interval and payment terms, and no price is listed here. The server process holds Stripe and Supabase secrets (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, SUPABASE_ANON_KEY) and writes invoice records durably to a JSON file (default ~/.invoice/invoice.json, configurable via INVOICE_DATA_PATH); one process should own that file and it should not…

Installation

In SourceWeft

  1. Open Invoice in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "invoice": {
      "type": "http",
      "url": "https://invoice-continuity2.vercel.app/mcp"
    }
  }
}

README

Invoice

Invoice keeps a freelancer's approved invoice — line items, quantities, the rate already approved, the due date, and late terms — then lets an assistant read that record before it answers. An assistant cannot add a line, change a rate, invent a discount, or move a due date unless that change is explicitly approved.

It works with ChatGPT, Claude, Gemini, Grok, and Cursor, plus any other MCP client that can do Streamable HTTP and OAuth. It is not a ChatGPT-only plugin.

Sign in with your Invoice account when the assistant opens OAuth. Do not paste an API key or password into a header. Invoice supports dynamic client registration: leave the client id and secret empty. The protected-resource metadata at /.well-known/oauth-protected-resource/mcp points clients at the OAuth issuer, which registers them.

Invoice tools need Pro or an active trial. A new subscription includes a 14-day trial. This page does not list a price. Checkout shows the billing interval and payment terms. Amounts stored on an invoice are the freelancer's approved figures, in whole minor units of the invoice currency. They are not a product price.

There is no hosted production domain in this repository. Run the server yourself and use the base URL you configure. The default MCP address is http://127.0.0.1:3000/mcp.

What the assistant can do

After you approve the connection, the server exposes these tools:

  • list_invoices
  • begin_invoice
  • read_invoice
  • place_line
  • describe_line
  • quote_line_rate
  • set_line_quantity
  • set_invoice_due
  • write_late_terms
  • offer_discount
  • seal_invoice
  • suggest_invoice_change
  • accept_invoice_change

read_invoice is the read the assistant should do before it answers. Draft figures are not an approved commitment. A suggested invoice change does not change the record. After the invoice is sealed, place_line refuses a new line, quote_line_rate refuses a changed rate, offer_discount refuses a discount, and set_invoice_due refuses a moved due date. Those changes go through suggest_invoice_change and then accept_invoice_change, and only when you explicitly approve that change.

The assistant only calls these tools when you and the host allow it.

Connect

Cursor, in ~/.cursor/mcp.json or a project .cursor/mcp.json:

json
{  "mcpServers": {    "invoice": {      "url": "http://127.0.0.1:3000/mcp"    }  }}

Do not add a headers block. Cursor registers a client and opens sign-in.

Claude Code:

bash
claude mcp add --transport http invoice http://127.0.0.1:3000/mcp

Do not pass an Authorization header. Other clients use the same address, choose OAuth, and leave client id and secret empty. Steps for ChatGPT, Claude, Gemini, Grok, and Cursor are on the connect page at /connect.

Registry metadata for this server is in server.json (io.github.LAHutchins91/invoice). The remote URL there is https://invoice-continuity2.vercel.app/mcp.

Run

bash
npm installnpm testnpm run typechecknpm run buildnpm start

When stdin is a terminal, Invoice serves Streamable HTTP on port 3000. When stdin is not a terminal, it speaks MCP over stdio and still opens the HTTP port. Logs during stdio mode go to stderr so they do not mix with the protocol.

Records are stored durably in a JSON file. The default path is ~/.invoice/invoice.json. Set INVOICE_DATA_PATH to move it. One server process owns that file. Do not point it at another product's data file.

OAuth uses the same idea as a Supabase authorization server with dynamic client registration. Set these on the server process, not in an MCP header:

  • APP_BASE_URL (default http://localhost:3000)
  • SUPABASE_URL
  • SUPABASE_ANON_KEY
  • STRIPE_SECRET_KEY
  • STRIPE_WEBHOOK_SECRET
  • STRIPE_PRICE_MONTHLY and STRIPE_PRICE_YEARLY (Stripe catalog ids, not prices)

Tool calls other than discovery require a signed-in account whose subscription status is active or trialing.

Source: README.md at commit c44bc9f

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.1LatestOct 5, 2026