Invoice Ninja MCP Server
Related Servers
Alternatives to Invoice Ninja MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Desktop to interact with Invoice Ninja v5, providing tools to read and write contacts, customers, quotes, projects, products, and optionally invoices, with configurable permissions.1MIT
- AlicenseBqualityDmaintenanceMCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.3222 npm2MIT
- AlicenseBqualityBmaintenanceConnects AI assistants to an Invoice Ninja v5 instance so users can query clients, invoices, quotes, payments, expenses, dashboard totals, and 25+ native reports in natural language. It runs read-only by default with opt-in writes, secret and bearer-link redaction, and LLM-friendly Markdown or compact JSON output.34MIT
- AlicenseBqualityBmaintenanceEnables managing invoices, estimates, customers, and dashboard/account data in a self-hosted invoicing system through 23 MCP tools, while automatically handling undocumented required API fields on writes.23MIT
- AlicenseAqualityCmaintenanceEnables LLM agents and MCP clients to interact with the Blesta billing API. It provides read-only tools for searching clients, invoices, services, transactions, and payment accounts, plus optional write tools for creating invoices, managing services, recording payments, and generating customer-facing payment links.33GPL 3.0
- FlicenseNot gradedqualityCmaintenanceHosted MCP server that enables AI assistants to manage clients, invoices, and expenses via the Invox API, supporting actions like drafting, sending, cancelling, and marking invoices as paid, as well as logging expenses and updating client information.-
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action: ping, get, list, or aggregate summary. List vs get pairs are clearly differentiated by their descriptions, and the outstanding summary is explicitly an aggregate over invoice listings.
Almost all tools follow a consistent in_verb_noun snake_case pattern, such as in_list_clients and in_get_invoice. The exceptions are in_ping, which lacks a noun, and in_outstanding_summary, which is not verb_noun, but the overall convention remains easy to follow.
Sixteen tools is slightly above the typical ideal range but reasonable for covering multiple Invoice Ninja resources. The set is broad without being overwhelming, and no tool appears redundant.
The surface is almost entirely read-only: it offers list/get operations plus a summary, but no create, update, delete, send, or payment-recording operations. For an Invoice Ninja server this is a significant gap, so agents cannot perform core lifecycle actions.