mcp-bigcapital
Related Servers
Alternatives to mcp-bigcapital
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to authenticate against an internal accounting web API, list companies, categories, bank transactions and documents, upload or batch-deposit receipts (idempotent, dry-run by default), set accounting metadata, and link documents to their matching bank transactions.MIT
- AlicenseBqualityAmaintenanceEnables 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

epago MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP-capable clients to read and write directly in epago accounting, including chart of accounts, transactions, invoices, payments, receipts, and tax reports.MIT- AlicenseAqualityCmaintenanceEnables MCP clients to read and write Bokio accounting data for one company through 85 tools covering invoices, customers, suppliers, journal entries, chart of accounts, fiscal years, items, tags, uploads, SIE export, and bank payments.40MIT
- FlicenseBqualityDmaintenanceBridges to a simple_invoicing FastAPI backend, exposing invoice, product, ledger, inventory, buyer, and payment management as MCP tools for use with MCP-compatible clients.15-
- AlicenseAqualityCmaintenanceEnables interaction with the IIT Roorkee Academics portal through MCP tools for authentication, academic data retrieval (fee, grades, transcripts), and safe API calls.24MIT
TDQS
Scored across 57 tools
Tools are generally named around distinct Bigcapital resources (vendor, customer, bill, invoice, expense, journal, receipt, payment, report), so an agent can usually tell them apart. The main ambiguities are between payments received and bill payments, and among status-changing actions like open_bill, publish_expense, and close_sale_receipt, but the descriptions are clear enough to resolve those.
Tool names consistently follow a lower_snake verb_noun pattern: list_*, get_*, create_*, update_* across resources, with a few expected domain verbs like open, publish, and close. Even compound resources like get_attachment_presigned_url still follow a predictable action-first structure.
With 57 tools, this is an extreme tool surface that will be costly for an agent to navigate and likely to cause misselection. Although the accounting domain is broad, this many operations should be split into focused server modules rather than exposed as one flat set.
The toolset covers a wide range of accounting lifecycles: customers, vendors, items, invoices, bills, expenses, receipts, payments, journals, attachments, and key financial reports. However, delete operations are almost entirely absent, and accounts are read-only (list/get but no create/update), leaving some workflows without full lifecycle support.