elba-mcp
Related Servers
Alternatives to elba-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude and Cursor to manage customers, create and update draft invoices, list or download invoices as PDF and XML e-invoices, and record and list payments in a BillingEngine account. It runs locally with your API key and never deletes data.1067 npmMIT
- AlicenseBqualityBmaintenanceEnables Claude and other MCP clients to manage a small-business back office, including clients, quotes, invoices, payments, reports, and PDF invoice export, while keeping data in a local SQLite file.21MIT
- 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
- AlicenseAqualityBmaintenanceLook up Russian companies by INN (tax ID) from Claude Desktop, Cursor or any MCP client: full company card, multi-year financials from official tax filings, bankruptcy and state-inspection history, trademarks and sanctions lists. Works without an API key — the anonymous free tier is enabled by default.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables creating, sending, and tracking invoices from MCP clients like Claude, Cursor, or Windsurf, using a hosted endpoint with API token.MIT
- FlicenseNot gradedqualityDmaintenanceHosted 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 19 tools
Most tools have clearly distinct purposes: creation flows are split between from-scratch (elba_create_act/elba_create_upd) and from-bill variants, and contractor find/get/create are distinguishable. The only mild fuzziness is in the reporting cluster (elba_unpaid, elba_report, elba_payment_news, elba_get_bill), which all surface bill/payment status, though descriptions do differentiate list vs aggregate vs news feed vs single bill.
All tools share a consistent elba_ prefix and snake_case, which makes the set easy to scan. Most are verb_noun (create_bill, act_from_bill, find_contractor), but several are bare nouns (organizations, templates, unpaid, report, payment_news), a minor deviation from the pattern.
At 19 tools the set is slightly on the heavy side, but the domain (bills, acts, UPDs, contractors, links, orgs, templates, reporting, INN lookup) legitimately needs this breadth. Each tool maps to a real operation, with no obvious filler.
Creation and read paths are well covered, but mutation is thin: no update/delete for contractors, no update/cancel/delete for bills, and acts/UPDs can be created but not fetched or listed by id. The elba_link_publish description references cancelled bills, yet no cancellation tool exists, which is a notable lifecycle gap.