@aiwerk/mcp-server-bexio
Related Servers
Alternatives to @aiwerk/mcp-server-bexio
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for the bexio API, enabling interaction with contacts, sales, accounting, projects, and more through 35 tools. Supports both PAT and OAuth authentication with read-only mode and tool group filtering.3521 npm4MIT
- AlicenseAqualityDmaintenanceA standalone MCP server for the bexio REST API, enabling interaction with bexio resources like contacts, invoices, and projects through natural language from any MCP client.2121 npmMIT
- AlicenseNot gradedqualityAmaintenanceComplete Swiss accounting integration for Bexio via MCP. Works with Claude Desktop, n8n, and any MCP client. 221 tools for invoices, contacts, projects & more. Created by Lukas Hertig.34MIT
- AlicenseCqualityCmaintenanceMCP server for smallinvoice.ch — Swiss SME invoicing and accounting with 146 tools and OAuth2 BYOC authentication.1009 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server exposing BuchhaltungsButler API tools for accounting, invoicing, and receipt management with curated, token-efficient endpoints.-
- FlicenseNot gradedqualityDmaintenanceA remote MCP server for the Moxie Public API, deployable to Cloudflare Workers. Exposes all 29 documented Moxie endpoints as MCP tools for managing clients, contacts, projects, tasks, invoices, payments, and more.-
TDQS
Scored across 310 tools
Multiple tools have overlapping purposes or unclear boundaries, such as the various position types (item_position, discount_position, pagebreak_position, etc.) and the duplicate paystub PDF tools (get_paystub_pdf vs get_pdf_for_employee_in_month). The 'expens' vs 'expense' naming further adds confusion.
While many tools follow a verb_noun pattern, there are significant deviations like create_expens, create_file_file, upload_manual_compound_entry_file_file, list_mes, and inconsistent use of 'list' vs 'search'. This mixed convention hurts predictability.
With 310 tools, the server is far too large for a coherent MCP interface. Even for a broad ERP system, this is excessive and likely overwhelms agents, making selection difficult.
The tool set covers a wide range of business domains (contacts, invoices, orders, projects, tasks, etc.), but there are gaps (e.g., no update for company_profile, no delete for business_activity) and redundancies that indicate incomplete or uneven coverage.