# InvoiceFlow Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## InvoiceFlow

Draft invoices and Stripe payment links for your clients, with you deciding when to send them.

- Record: https://musedirectory.ai/connector/invoiceflow
- Category: Finance & Bills
- Developer: EarthyPunyapat (https://invoiceflow-ten-azure.vercel.app)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 359ms, checked 2026-11-02T02:11:24Z
- Endpoint: https://invoiceflow-ten-azure.vercel.app/api/mcp
- Auth: Needs an access key; Pricing: unknown
- Screening: Screened, no issues found (2026-11-02T02:11:24Z)
- Source: Found in the official MCP Registry (io.github.EarthyPunyapat/invoiceflow) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.EarthyPunyapat%2Finvoiceflow

Connects Muse to an InvoiceFlow account. Muse can check and create client records, draft invoices with line items, list invoices by status, and fetch a Stripe Checkout payment link to share. Drafts are not emailed, so you send them yourself. Requires an InvoiceFlow API key.

Example request: "Draft a $2,500 invoice for Maria Chen's website redesign, due in 30 days, and give me the payment link."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use InvoiceFlow to help me. It is a free service with an MCP server at https://invoiceflow-ten-azure.vercel.app/api/mcp. It needs an API key from EarthyPunyapat; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- invoiceflow_whoami: Check which InvoiceFlow account this key belongs to and that the key works. Call this first; it is the cheapest way to fail early.
- invoiceflow_create_client: Create a customer record. A client is required before an invoice can be created. Returns the new client id.
- invoiceflow_list_clients: List existing clients. Use this before create_client to avoid making duplicate customer records.
- invoiceflow_create_invoice: Create a DRAFT invoice for an existing client. Amounts are INTEGER CENTS: unitPrice 25000 means $250.00, not $25,000. Do not send totals - the server derives subtotal and total from the line items. Does not email anyone.
- invoiceflow_list_invoices: List invoices with their status and totals. Invoices belonging to other accounts are not visible and return as absent, not as errors.
- invoiceflow_get_invoice: Fetch one invoice by id, including line items and derived totals.
- invoiceflow_share_invoice: Get the payable Stripe Checkout link for an invoice. This is what you give a human so they can actually pay. Does not email anyone.

Screening checks:
- MCP handshake: pass (Answered in 359ms)
- Domain against threat feeds (Cloudflare security DNS): pass (invoiceflow-ten-azure.vercel.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (7 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)
