Billstride
Server Details
Create, send and track invoices from a conversation in Claude, ChatGPT or any MCP client that supports OAuth. Draft an invoice from one sentence or from last month's invoice for the same client, finalize it, email it to your client and send payment reminders for overdue ones. See revenue by month and by client, download PDFs and e-invoices (ZUGFeRD, XRechnung), and export DATEV packages for your tax advisor. Invoices follow the tax rules of 25 countries, including reverse charge and the small-business VAT exemption. New invoices are drafts, and nothing is emailed until you ask. Pay per invoice with no subscription: the first invoice is free.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- Billstride
TDQS
Scored across 27 tools
Most tools are clearly separated by resource and action, and the descriptions explicitly contrast close pairs such as create_invoice vs create_invoice_from_previous vs duplicate_invoice, list_customers vs list_recipients, and get_invoice vs get_invoice_pdf vs get_invoice_preview. With 27 tools there are still several adjacent invoice/customer operations that could cause brief hesitation, but the boundaries are documented.
Every tool uses snake_case with a leading verb and a predictable resource noun. Multi-part names like get_invoice_pdf and create_invoice_from_previous remain readable and consistent with the rest of the set.
27 tools is heavy for an MCP server, even a broad invoicing platform. Most tools address real needs, but the surface is borderline bloated and some listing, reporting, and invoice-creation variants could likely be consolidated.
The surface covers customer and invoice CRUD, finalization, duplication, PDF/e-invoice access, email history, reminders, sender settings, credits/vouchers, DATEV export, and reporting. Minor gaps remain around recording payments/marking invoices paid, creating credit notes, and managing recurring invoice templates, which are referenced but not exposed as tools.
Publisher details
- Operator
- superview llc · Publisher source
- Operator website
- https://billstride.com
- Vendor relationship
- First-party
- Documentation
- https://billstride.com/mcp
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- Requires a Billstride account (open sign-up, no admin approval). The first invoice is free; after that each finalized invoice is paid from prepaid credit bought on billstride.com. No subscription. Drafts, reading and exports cost nothing. · Publisher source
Available Tools
27 toolscreate_customerCreate customerAIdempotentInspect
Creates a customer record from a company name and, optionally, an address, VAT ID and email. Use it to store a client before their first invoice. The company name is unique in the account, compared exactly after trimming: a call with a name already in use is rejected and adds nothing, so repeating a call that succeeded leaves no duplicate. A DATEV debtor number is assigned automatically, the next one after the highest in use, and cannot be chosen. The VAT ID is stored as given, without a format check. It creates no invoice. create_invoice does not need this tool first: it takes the recipient details as fields and creates the customer record itself when none exists under that name. It does not email anyone.
Inputs: companyName (required), city, email, state, +5 more.
create_invoiceCreate invoiceADestructiveInspect
Creates a new invoice from the given recipient, line items and discounts. Use it for a new invoice written from scratch; for a repeat of earlier work use create_invoice_from_previous. By default it creates a draft, which is free and can still be edited or deleted; a finalized invoice cannot be deleted. With isDraft=false it creates a finalized invoice and spends credits. Finalizing uses one free invoice if any remain, otherwise it deducts the per-invoice price from the credit balance. It fails when the balance is too low, and the charge is not refunded. invoiceDate and dueDate are written in the sender's date format, the dateFormat field of get_sender_settings (for example DD.MM.YYYY). A date that cannot be read as day, month and year in that format is rejected. The check goes no further: a date written in another format with the same separator is read in the expected order (03/04/2026 is 3 April in DD/MM/YYYY and 4 March in MM/DD/YYYY), a day past the end of its month rolls into the next one (31.02.2026 becomes 3 March), and a two-digit year is read as 19xx (26 is 1926). Left out, they default to today and today plus the payment terms; currency, VAT rate and style default from the sender settings, which must already exist. Line item prices take unitPrice (decimal, e.g. 110.00) or unitPriceCents (integer, e.g. 11000); VAT rates are basis points (1900 = 19%). Side effect: the recipient gets a customer record if none exists under that company name, created from the recipient details of the invoice, and the invoice is linked to it. An existing customer record is not changed. It does not email anyone. Each call creates another invoice, so repeating a call that succeeded leaves a duplicate.
Inputs: dueDate, isDraft, currency, discounts, +17 more.
create_invoice_from_previousCreate invoice from previousADestructiveInspect
Creates a new invoice by copying the most recently created invoice for a recipient (exact company name): its recipient details, line items and discounts. Use it for recurring work, such as the same invoice as last month with different hours. Invoice number, dates, line items, currency, VAT rate, shipping, note, style and buyer reference can be overridden; recipient details and discounts cannot; update_invoice can change those afterwards. invoiceDate and dueDate are written in the sender's date format, the dateFormat field of get_sender_settings (for example DD.MM.YYYY). A date that cannot be read as day, month and year in that format is rejected. The check goes no further: a date written in another format with the same separator is read in the expected order (03/04/2026 is 3 April in DD/MM/YYYY and 4 March in MM/DD/YYYY), a day past the end of its month rolls into the next one (31.02.2026 becomes 3 March), and a two-digit year is read as 19xx (26 is 1926). By default it creates a draft, which is free. With isDraft=false it creates a finalized invoice and spends credits. Finalizing uses one free invoice if any remain, otherwise it deducts the per-invoice price from the credit balance. It fails when the balance is too low, and the charge is not refunded. It fails if the recipient has no earlier invoice. Side effect: the recipient gets a customer record if none exists under that company name, created from the recipient details of the invoice, and the invoice is linked to it. An existing customer record is not changed. It does not email anyone. Each call creates another invoice.
Inputs: recipientCompanyName (required), dueDate, isDraft, currency, +8 more.
delete_customerDelete customerADestructiveIdempotentInspect
Permanently deletes one customer record, chosen by id. Use it to remove a client that was entered by mistake or is no longer needed. It cannot be undone. A customer with a finalized invoice cannot be deleted: the call is rejected and nothing changes, because the debtor number of the record identifies those invoices in export_datev and a recreated record would get a different number. A customer with only drafts, or with no invoices, can be deleted. No invoice is deleted or altered: Invoices and recurring invoice templates keep the recipient details they were created with and only lose their link to the record. Repeating the call deletes nothing further and returns an error. It does not email anyone.
Inputs: id (required).
delete_invoiceDelete invoiceADestructiveIdempotentInspect
Permanently deletes one invoice together with its line items and any PDF uploaded for it. Use it to remove a draft the user no longer wants, or an imported invoice that nothing depends on. It cannot be undone. Only drafts and unused imports can be deleted: an imported invoice that has an email, a reminder, a payment or a credit note is rejected, and so is any invoice finalized here, which stays on record and is cancelled with a credit note. The credit spent on an import is not refunded. It does not email anyone.
Inputs: id (required).
duplicate_invoiceDuplicate invoiceAInspect
Creates a draft copy of one existing invoice, chosen by id, with the same recipient, line items and discounts, today's date, a due date from the payment terms and the current sender details. Use it to reuse a specific invoice; create_invoice_from_previous copies the latest invoice of a recipient instead and can override fields. The copy is always a draft, so it is free and spends no credits, whatever the status of the original. It has no invoice number; update_invoice can set one and finalize it. Each call creates another draft, so repeating a call that succeeded leaves a duplicate. Side effect: the recipient gets a customer record if none exists under that company name, created from the recipient details of the invoice, and the invoice is linked to it. An existing customer record is not changed. It does not email anyone.
Inputs: id (required).
export_datevExport to DATEVAIdempotentInspect
Builds a DATEV export (booking batch and master data CSV files) for the finalized invoices dated between from and to, both ISO dates (YYYY-MM-DD), whatever the sender's date format, and returns it as a base64-encoded ZIP with counts and warnings. Use it when the user or their tax advisor needs the bookkeeping export. Only for accounts with a German sender address and DATEV consultant and client numbers set in the sender settings. Side effect: before exporting it creates a customer record with a debtor number for every invoice recipient that has none and links the invoices to it; nothing is overwritten or deleted, and repeating the call adds nothing further. It does not email anyone.
Inputs: to (required), from (required).
get_balanceGet credit balanceARead-onlyIdempotentInspect
Returns the account's prepaid credit balance in integer cents, the same amount formatted, and the number of free invoices left. Use it before finalizing an invoice to check the charge can be covered. Read-only.
Inputs: no named parameters.
get_client_insightsGet client insightsARead-onlyIdempotentInspect
Summarizes the finalized invoices for one client (exact company name): count, total and average in cents, first and last invoice dates, the five most common line items with their latest price, and how many emails were sent. Use it to answer questions about a client or to pick prices for their next invoice. Read-only. Drafts are ignored, amounts in different currencies are added without conversion, and it returns an error when the client has no finalized invoice.
Inputs: recipientCompanyName (required).
get_customerGet customerARead-onlyIdempotentInspect
Returns one customer record in full: company name, address, VAT ID, email and DATEV debtor number, with the number of invoices linked to it and the 10 most recent of them (id, number, dates, total in cents, status, paid status). Use it to get the recipient details for create_invoice, which takes them as fields and not as a customer id, or to see the stored values before update_customer. Read-only. Takes a customer id from list_customers; it cannot look up by name. The invoice count and list can be incomplete. They cover the invoices linked to the customer record, drafts and credit notes included. An invoice is linked by exact company name when it is created or edited. list_invoices filtered by recipient name finds every invoice.
Inputs: id (required).
get_email_historyGet email historyARead-onlyIdempotentInspect
Lists the emails sent for one invoice, including payment reminders, with recipient, subject, message and the times each was sent, delivered, opened or bounced. Use it to check whether an invoice reached the customer before sending it again or sending a reminder. Read-only. Delivery and open times depend on the email provider reporting them and can be missing.
Inputs: invoiceId (required).
get_invoiceGet invoiceARead-onlyIdempotentInspect
Returns one invoice in full: sender and recipient details, dates, totals in cents, line items, discounts and recorded payments. Use it to review an invoice, or to get the complete current values that update_invoice needs sent back. Read-only. Takes an invoice id from list_invoices; it cannot look up by invoice number.
Inputs: id (required).
get_invoice_pdfGet invoice PDF or e-invoiceARead-onlyIdempotentInspect
Returns a download link for an invoice, not the file itself: as a PDF (the default), as a ZUGFeRD PDF with the e-invoice data embedded, or as XRechnung XML. Use it when the user wants to see or save the document, for example to check a draft before finalizing, or needs an e-invoice for a business customer. The link works for 15 minutes without signing in: whoever has the link can download the document until it expires. Read-only: nothing is stored or sent. A draft PDF is watermarked DRAFT, and an imported invoice gives the PDF that was uploaded. The e-invoice formats exist for finalized invoices only and need the fields the standard requires; when one is missing the tool returns an error naming it instead of a link. Recipient fields and the buyer reference can still be changed on a finalized invoice, while sender details are fixed when an invoice is created.
Inputs: id (required), format.
get_invoice_previewPreview invoice pageARead-onlyIdempotentInspect
Returns one page of an invoice as a JPEG image, about 1000 pixels on the long edge, with the page number and the page count. Use it to look at how an invoice or a draft is laid out and what is on it; it is an image of the page, not the document itself, and get_invoice_pdf gives the file to save or pass on. It shows the first page unless page is given, and a page past the end is rejected with the page count. A draft is shown with a DRAFT watermark. The image is reduced, so small print can be hard to read: get_invoice has the exact values. Read-only: nothing is stored or sent. Previews are rate-limited per account, and a call over the limit is rejected with the time to wait.
Inputs: id (required), page.
get_revenue_summaryGet revenue summaryARead-onlyIdempotentInspect
Summarizes invoiced revenue for one calendar year (default: the current year): the total in cents, a month-by-month breakdown and the ten largest clients. Use it for questions about turnover. Read-only. It counts finalized invoices by invoice date, leaves out drafts and imported invoices, says nothing about whether invoices were paid, and adds different currencies together unless a currency filter is given.
Inputs: year, currency.
get_sender_settingsGet sender settingsARead-onlyIdempotentInspect
Returns the account's sender settings: company name and address, email, tax and VAT IDs, bank details, invoice defaults (VAT rate, payment terms, style, currency, pricing mode, number locale, date format, note), reminder settings and DATEV numbers. Use it to learn the date format that invoiceDate and dueDate take in create_invoice and create_invoice_from_previous, to see the defaults applied when a field is left out, or to show the user what is printed on their invoices. Read-only. It returns an error for an account that has not finished onboarding in the web app.
Inputs: no named parameters.
get_transaction_historyGet credit transactionsARead-onlyIdempotentInspect
Lists the account's credit ledger, newest first: invoice charges, top-ups, voucher redemptions and refunds, each with the amount in cents and the balance afterwards. Use it to explain a balance or find what an invoice cost. Read-only. Returns at most 100 entries per page and covers Billstride credits only, not payments customers made on invoices.
Inputs: page, limit.
list_customersList customersARead-onlyIdempotentInspect
Lists the account's customer records sorted by company name: id, company name, city, country, email and VAT ID, with the number of invoices of each and their totals in cents per currency. Use it to find a customer id or to see the account's clients, including ones that were never invoiced. Read-only. Returns 50 per page by default and at most 100, paged by page number; search keeps the company names that contain the given text. The counts and totals are not revenue figures. They cover the invoices linked to the customer record, drafts and credit notes included. An invoice is linked by exact company name when it is created or edited. list_recipients reads the same kind of details off each recipient's latest finalized invoice instead and has nothing for a customer without one. get_customer returns the full address.
Inputs: page, limit, search.
list_invoicesList invoicesARead-onlyIdempotentInspect
Lists invoice summaries (number, recipient, dates, total in cents, currency, status, paid status) with filters for type, recipient, invoice number and date range, sorted by date or amount. Use it to find an invoice id, the most recent invoice or client, or to review drafts, unpaid or overdue invoices. Read-only. dateFrom and dateTo are ISO dates (YYYY-MM-DD), whatever the sender's date format. Returns at most 100 per call, paged by page number or cursor, and no line items; get_invoice returns those.
Inputs: page, limit, cursor, dateTo, +6 more.
list_recipientsList recipientsARead-onlyIdempotentInspect
Lists the customers the account has invoiced, each with the address, VAT ID, email and invoice number from their latest finalized invoice. Use it to look up a customer's details before creating an invoice. Read-only. The list is sorted by company name and carries no dates, so it does not show who was invoiced most recently. Recipients that only appear on drafts are not included, and the list is not paginated.
Inputs: no named parameters.
redeem_voucherRedeem voucherADestructiveIdempotentInspect
Redeems a voucher code and adds its amount to the account's credit balance. Use it when the user gives a voucher code to apply. A redemption cannot be reversed and uses up one of the voucher's limited redemptions. Each voucher works once per account, so repeating the call adds nothing and returns an error. It fails for an unknown, inactive, expired or used-up code, or when the voucher's currency differs from the account's billing currency.
Inputs: code (required).
send_invoiceEmail invoiceADestructiveInspect
Emails a finalized invoice as a PDF attachment to the address given in "to", with the given subject and optional message. Use it to deliver an invoice to a customer. The email goes to a third party and cannot be recalled, and every call sends another email. The invoice must already be finalized: this tool does not finalize a draft and does not spend credits. An account can send at most 50 emails in 24 hours, and at most 5 per invoice and 5 per recipient address. The send is recorded in the email history, and the address is saved as the invoice's recipient email if it had none.
Inputs: to (required), subject (required), invoiceId (required), message.
send_reminderSend payment reminderADestructiveInspect
Emails a payment reminder, with the invoice PDF attached, to the recipient email stored on the invoice. Use it to chase an unpaid invoice. The email goes to a third party and cannot be recalled. It fails if the invoice is not finalized, is a credit note, is paid, is not past its due date or has no recipient email, and a second reminder for the same invoice shortly after the last one is refused. Without a tier it sends the tier the automatic reminders would send now (friendly, second_notice, final_notice) and fails if none is due yet. With a tier it sends that tier whatever the day thresholds say, and fails if that tier was already sent; get_email_history lists the reminders already sent. The remindersEnabled setting of the account only governs the automatic reminders and does not stop this tool, and neither does the reminders switch on the invoice itself. The wording of the reminder cannot be changed. The reminder is recorded in the email history.
Inputs: invoiceId (required), tier.
suggest_invoice_numberSuggest next invoice numberARead-onlyIdempotentInspect
Suggests the next invoice number by incrementing the trailing number of the latest numbered invoice, for one recipient (exact company name) or across all invoices. Use it before creating or finalizing an invoice that needs a number. Read-only: it does not reserve the number or check that it is unused, and it returns no suggestion when there is no numbered invoice to continue from.
Inputs: recipientCompanyName.
update_customerUpdate customerADestructiveIdempotentInspect
Changes one customer record, chosen by id. Use it to correct a company name, address, VAT ID or email. Only the fields given are changed, but each one overwrites the stored value and the old value is not kept; an empty string clears a field, except the company name. No invoice is altered: Invoices and recurring invoice templates keep the recipient details they were created with. A company name another customer in the account already has is rejected and nothing is saved. The debtor number cannot be changed. The VAT ID is stored as given, without a format check. Saving an invoice for the same company name in the web app overwrites the record's address, VAT ID and email with that invoice's recipient details. It does not email anyone.
Inputs: id (required), city, email, state, +6 more.
update_invoiceUpdate invoiceADestructiveInspect
Replaces an existing invoice with the values given. Use it to edit a draft, to finalize a draft (isDraft=false), or to correct the recipient details, buyer reference, note or style of a finalized invoice. On a draft this is a full replacement, not a partial update: all line items and discounts are deleted and recreated from the input, the amounts are recalculated, and any field left out is reset to empty or to the sender-settings default. On a finalized invoice the invoice number, invoice date, currency, shipping, the invoice-level discounts, the number of line items and each line's quantity, unit, price, VAT rate and discount are locked: a call that changes any of them is rejected and nothing is saved. Recipient details, buyer reference, note, style, due date and line item titles and descriptions can still change. A finalized invoice keeps the amounts it was issued with: its totals and line amounts are never recalculated and its line items and discounts are never deleted or recreated. lineItems and discounts left out stay as stored; when they are sent, they are matched to the stored rows by position, and only a line's title and description and a discount's label are written. A field left out keeps its current value, and an empty string clears an optional text field (street, second address line, state, VAT ID, email, buyer reference, note); company name, postal code, city and country cannot be emptied. get_invoice returns the current values to send back. invoiceDate and dueDate are written in the date format stored on the invoice, the dateFormat field of get_invoice, which can differ from the sender's current format and is not changed by this tool. A date that cannot be read as day, month and year in that format is rejected. The check goes no further: a date written in another format with the same separator is read in the expected order (03/04/2026 is 3 April in DD/MM/YYYY and 4 March in MM/DD/YYYY), a day past the end of its month rolls into the next one (31.02.2026 becomes 3 March), and a two-digit year is read as 19xx (26 is 1926). Left out on a draft, they are not kept: they are reset to today and today plus the sender's payment terms. Left out on a finalized invoice, they stay as stored. Finalizing a draft spends credits. Finalizing uses one free invoice if any remain, otherwise it deducts the per-invoice price from the credit balance. It fails when the balance is too low, and the charge is not refunded. A finalized invoice cannot go back to draft. With isDraft left out the invoice keeps its current status: a draft stays a draft and a finalized invoice stays finalized. Editing a finalized invoice changes a document the recipient may already have, and the previous values are not kept. Line item prices take unitPrice (decimal, e.g. 110.00) or unitPriceCents (integer, e.g. 11000); VAT rates are basis points (1900 = 19%). Side effect: the recipient gets a customer record if none exists under that company name, created from the recipient details of the invoice, and the invoice is linked to it. An existing customer record is not changed. It does not email anyone.
Inputs: id (required), dueDate, isDraft, currency, +18 more.
update_sender_settingsUpdate sender settingsADestructiveIdempotentInspect
Changes the account's sender settings: company and address, tax and VAT IDs, bank details, invoice defaults (VAT rate, payment terms, style, currency, number and date format, note) and DATEV numbers. Use it to change any of these; get_sender_settings returns the current values. Only the fields given are changed, but each one overwrites the stored value and the old value is not kept, which matters most for bank details printed on invoices. New invoices use the new values; existing invoices keep the sender details they were created with. It cannot create settings for an account that has not finished onboarding in the web app.
Inputs: bic, city, iban, email, +25 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Send invoices from Claude and ChatGPT. One sentence becomes a PDF with a Stripe payment link.
Create EU-compliant invoices, manage clients and download PDFs from your AI assistant.
Make PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.
Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceCreate German invoices (§14 UStG) via Claude or any MCP-compatible AI by describing the invoice in natural language.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage e-invoices through natural language, supporting EU compliance formats like ZUGFeRD and XRechnung, as well as US plain PDF invoices.7-
- FlicenseNot gradedqualityBmaintenanceEnables time tracking and invoicing through natural conversation with MCP clients like Claude or ChatGPT, allowing users to log work hours, query unbilled time, and draft invoices, with a minimal web app for settings, CSV import, and Stripe-powered billing.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage compliant e-invoicing (Factur-X, EN 16931) by creating, issuing, sending, and tracking invoices, quotes, and retainers through natural language via the Model Context Protocol.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.