Hosted billing MCP server for a compatible AI assistant. Supports invoice and estimate creation, PDF generation from saved company templates, client and item management, and unpaid balance or sales queries. This can support an advisory practice or small business with service invoicing and fee records. OAuth authorizes access to the connected company. Codex is tested. Sending requires confirmation; recording a payment does not transfer funds. This is billing software, not portfolio management or investment advice. Currently free.
invoicingestimatesbillingfee recordssmall business
Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers →All seven roles →
Vendor-reported: features and the free price come from the submitter. The endpoint returned an authorization challenge when checked on October 6, 2026, consistent with the stated OAuth flow.
This server can write: it creates invoices, estimates, clients and items, and records payments. Sending requires confirmation per the vendor; recording a payment does not move money.
Only Codex is stated as tested; behavior in other AI clients is unconfirmed.
Billing software, not portfolio management, fee-billing reconciliation against custodial data, or investment advice. Advisory fee calculations remain your firm's responsibility.
Pricing is described as currently free and may change.
Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server
How to connect Pocket Invoice MCP
Step 1
Remote server: paste a URL
Pocket Invoice MCP publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.
Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.
Step 3
Verify, then widen access
Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.
Read-only: review my P&L and balance sheet for <period> from the accounting system and reconcile them against the bank and account-aggregation feeds for the same period. List items a buyer would question, personal expenses run through the business, uncategorised transactions, owner compensation treatment, one-off items, plus any transaction visible in the bank feed with no matching entry in the books. Output Item / Amount / Where it appears / Why a buyer asks. Do not post, edit or reclassify anything.
Guardrail · Read-only. Any adjustment goes through your accountant, not a chat tool.
Build a diligence readiness checklist across client, financial, custody and compliance records. For each item say whether it exists today, where it lives, and what work is needed. Use read-only access, keep client identities out of the output, and do not create or share a data room or upload any document.
Guardrail · Read-only. Never let a tool export client data to an external destination.
Read-only, in three passes. First gather my practice's own figures: households, AUM, recurring vs. one-time revenue, fee mix, client age distribution and top-10 concentration from CRM and custody, and revenue, expenses, owner compensation and margin from the accounting system, record where each figure came from and mark anything you could not source rather than estimating it. Second, run those inputs through ValuationMCP's guided valuation workflow, keeping the source note attached to every input you pass in and showing the methods, the range and the assumptions behind it. Third, pull the filed peer distribution for my state and AUM band from ADVmcp and use it to sanity-check the gathered inputs, client counts, account counts, custody arrangement, disclosure history, and to place my result in context. Output the valuation range, the inputs table with sources, and where the practice sits against filed peers. No client names or account numbers anywhere in the output, and do not write, export or share anything.
Guardrail · Read-only, no client identities in the output. The valuation is a modeled estimate, not an appraisal, and peer percentiles are positions rather than grades: Form ADV carries no revenue, EBITDA or margin figures, so peer data contextualises the number and never moves it.
