Morning (Green Invoice) MCP
Related Servers
Alternatives to Morning (Green Invoice) MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects AI assistants to the Danish accounting platform Billy (billy.dk) for managing invoices, journal entries, balances, and receipts, with built-in human approval for all write operations.4042 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read a company's accounting data — customers, vendors, items, accounts, invoices, estimates, payments, bills, purchases, journal entries, time activities, attachments and financial reports — through the QuickBooks Online Accounting API v3. On explicit request it can also create, update and void records, email invoices and upload attachments, using per-request OAuth headers for stateless, multi-tenant operation.Apache 2.0
- AlicenseBqualityAmaintenanceEnables AI assistants to query and manage self-hosted accounting data—invoices, balances, and books—through natural language, with read-only tools by default and optional scoped write operations.3025 PyPI1AGPL 3.0
- FlicenseBqualityBmaintenanceConnects AI assistants to Big Red Cloud accounting data, enabling read-only lookups and safe write operations with confirmation drafts.100-
- AlicenseBqualityCmaintenanceConnects AI assistants to Mintline receipts and transactions via the Model Context Protocol. It enables users to search, filter, and manage financial records, including matching receipts with bank transactions through natural language.3677 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query a connected accounting platform for organisations, invoices, contacts, chart of accounts, and profit-and-loss reports, supporting bookkeeping, AR/AP, and financial reporting workflows.196 npmMIT
TDQS
Scored across 21 tools
Overlap is significant: prepare_document, save_document_draft, prepare_issue_document_draft, prepare_morning_action, and prepare_expense_upload all involve preparing, saving, or executing actions/drafts. read_morning, api_operations, and api_operation_schema also blur read/meta boundaries. Descriptions attempt to clarify, but an agent can easily misselect between local draft preparation, Morning draft issuance, and generic reviewed operations.
All tool names use lower snake_case, so the surface is predictable. However, it mixes verb_noun action names such as search_clients, get_document, and save_document_draft with noun-only meta names such as document_options, connection_status, api_operations, and request_status.
At 21 tools, this is borderline heavy for the domain and reflects a layered draft/prepare/execute/generic-API workflow. Many tools earn their place, but the set feels over-fragmented and could likely be consolidated.
Core lifecycle is covered: document drafting, preview/issuance preparation, execution, expense staging/upload, client and document search/get, and reviewed generic writes. Some direct CRUD conveniences are missing, but generic write paths and schema discovery allow workarounds.