moneys3-mcp
Related Servers
Alternatives to moneys3-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes the Moloni ON GraphQL API to AI clients, providing a curated set of operations as typed and documented tools.-
- FlicenseBqualityDmaintenanceMCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.1527 npm-
- AlicenseAqualityBmaintenanceMCP server for the Elorus invoicing and accounting platform, enabling AI assistants to create invoices, manage contacts, and query financial data through natural language.434MIT
- AlicenseAqualityBmaintenanceMCP server for VoxFactura enabling AI assistants to query business data (invoices, expenses, project margins, clients, VAT) and create draft quotes or mark invoices paid via a scoped API, with no direct client sends.11MIT
- AlicenseNot gradedqualityDmaintenanceMCP server enabling AI assistants to manage invoices, contacts, products, and other accounting data through the Bukku API.6MIT
- AlicenseBqualityCmaintenanceA read-only MCP server for SimpleShop accounting data, enabling AI agents to find documents, download PDFs, inspect products, and review sales exports.5MIT
TDQS
Scored across 61 tools
Most tools map clearly to a specific entity and action, but several names overlap conceptually: m3_activities vs m3_crm_activities, m3_stock_documents vs m3_inventory_documents, and m3_delete_invoice next to the issued/received invoice tools. Descriptions usually resolve the ambiguity, but the boundaries are not always obvious at a glance.
The m3_ prefix and the m3_create_* / m3_delete_* conventions are applied consistently, while read tools mostly use plural resource nouns like m3_orders and m3_receivables. Minor exceptions such as m3_graphql, m3_connection_test, and m3_set_agenda break the pattern slightly but do not make the set unpredictable.
61 tools is far beyond the typical well-scoped MCP surface and creates a heavy navigation burden for an agent. The high count is purposeful given the breadth of an ERP system, but it still feels oversized for a single MCP server.
The server covers many Money S3 modules with query/create/delete operations for most resources, but there are no built-in update tools anywhere and some areas are one-sided, such as wages being create-only and orders/employees/service records being read-only. The raw m3_graphql tool provides an escape hatch, but the exposed surface is not a complete lifecycle.